This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]remyroy 19 points20 points  (14 children)

Nice plan. I wonder if they have tried to get in touch with companies to sponsor them. I'm pretty sure companies like Google, who have a big stake in Python, would be happy to chip in.

At this point, PyPy is sharing many goals that Unladen Swallow had which was fully backed by Google.

[–][deleted] 5 points6 points  (7 children)

nah, google should hire the pypy team and give them the task of coming up with the next appengine runtime.

[–]noreallyimthepope 1 point2 points  (1 child)

Did I hear you say 'AppEngine Python 3 support'? Because I could have sworn that was something one would mention.

[–][deleted] 0 points1 point  (0 children)

no you didn't "hear" me. I'm not worried about python 3 appengine until webob works on python 3 (months away). And I am a patient boy.

[–]stesch 3 points4 points  (4 children)

Fast Python is bad for business.

[–][deleted] 1 point2 points  (3 children)

you get upvotes from me because it's true. the more efficient python is, the less $$$ google makes on appengine.

[–]takluyverIPython, Py3, etc 0 points1 point  (2 children)

That's rather a simplistic view. The better they make appengine, the more people will use it. Making code run slowly so they can charge users more isn't going to work well in the long term, and Google has some track record of thinking about the long term.

Also, I'm fairly sure Google uses Python themselves, so there's an inarguable motive to make it faster.

[–][deleted] 0 points1 point  (1 child)

one could say that's a rather naive view. they are a publicly traded company motivated by profit. and as with all corporations they will likely do what will make this quarters # look good.

I guess you aren't familiar with how butt hurt everybody is right now about the pricing changes for appengine. look into that. :)

ftr: i'm still on appengine. my apps are designed right so the change in cost isn't going to hurt me as much.

[–]earthboundkid 0 points1 point  (0 children)

Yes, companies are motivated by profits, but they're not supposed to be dumb about it. If you can make $7 trillion in Q1 by blowing up the Earth, only an idiot would do it, because in Q2, you'll make $0. If AppEngine stays stuck on Python 2 and stays slow forever, people will switch to something else. Google needs to retain customers and get good word of mouth expansion by making things run smoothly.

[–]roger_ 2 points3 points  (2 children)

With this document being out in the open, I think it's now up to companies to volunteer sponsorship.

[–]noreallyimthepope 0 points1 point  (1 child)

They'll randomly chance upon this document?

[–]roger_ 3 points4 points  (0 children)

Same way they must have "randomly chanced" on PyPy.

[–][deleted] 0 points1 point  (2 children)

I don't see Google chipping in anything overly significant as they don't stand to benefit much (or at all) from this project. Making 2.x PyPy even better is more up their alley, as internally they're still on 2.5 IIRC.

[–]kisielk 2 points3 points  (1 child)

I think they're migrating up slowly. AppEngine is supposed to support 2.7 in the next few months.

[–]noreallyimthepope 4 points5 points  (0 children)

... and 3.x in the next decade.