I don't really understand the politics surrounding Python, but I don't understand why they believe this could be "blessed" by inclusion into the repository.
Performance goals have not been met so far; it increases memory usage; PyPy is an alternative with more community support (if only because the typical Python programmer knows more Python than C++); and it makes the code much more complex, introducing lots of hard-to-debug problems, at a time when the developers already have trouble getting people to migrate to 3.x.
The 3.x branch does not need a reputation for instability.
(None of this is to say Unladen Swallow is a bad idea, or should be killed; but it should prove its worth first.)
> but I don't understand why they believe this could be "blessed" by inclusion into the repository.
Google is, of course, a big company with lots of very smart people, and they rely on Python (and probably want to rely on it more in the future). Given that they employ Guido and also the primary developers of Unladen, the chances are very good that they will continue to vigorously improve upon it until their performance goals are met.
Hmm, yes, I understand why the Unladen Swallow developers, and to a certain extent Google, would want to do that. It just seems to me that the community would benefit more by waiting a little.
By the developers' own admission, LLVM's JIT infrastructure is immature and integrating it with Python uncovered lots of issues. Sure, clang has pretty good community support, but that doesn't mean that the Python integration - or even the JIT stuff - is equally well-supported. And the Python community doesn't contain many LLVM experts, I'd wager.
Very simple: this is a PEP to improve the state of "Cpython" (this is the main python implementation right now, and has been since the invention of python).
Pypy, on the other hand, is a new implementation of Python (just like ironpython or jython), and it could eventually replace cpython in the future if it proves to be succesfull (although it would be a long way off).
In few words: Python, the language, have many implementations. Cpython is the current reference one. Unladen Swallow aims to improve it, not to replace it.
Actually, even the US developers acknowledge that Pypy (or any other succesfull implementation that may come up) is the future, because it doesn't have to bear the burden imposed by the c platform.
This is speculation, but: Google is paying some people actual money to work on Unladen Swallow. People who have made bold claims about the performance improvements, which, apparently, were not entirely justified.
I imagine that it would be politically desirable to show success by getting officially blessed, and it would also mean that the project wouldn't just stagnate if the people now working on it were told to do something else.
More optimistically, they acknowledge that more coders would be welcome, and hope that it's easier to find those after being included in the main repository. It would also give them an edge over PyPy, their sort-of-competitor.
I don't think it's enough to just add JIT. For a runtime system the garbage collector is important, it's important to do optimizations such as V8's hidden classes, function inlining, to remove the GIL etc. This is probably the reason why their perfomance gain is so small - - they have added JIT, while applying only a few smart optimizations.
I don't think Unladen Swallow should be merged into CPython until the benefits are proven. Currently it will just add an extra layer of complexity, worsen Python's greedy management of memory and add little benefits in perfomance.
So is the goal to gain resources by becoming part of CPython? It seems like the small performance increases they got are completely overshadowed by the additional memory requirements. I don't pretend to understand the mainline Python development cycle, but this surely doesn't seem mature enough to justify declaring it as "the way forward".
Ya I noticed that too. I'd love to have some performance benefits from JIT too but not at those costs. 2.43x - 2.76x increase in memory to Django[1]. Ugh. That's a large enough change that I'd have to upgrade hardware. Come on now.
Down further they say something about how they'll ask the community what the acceptable memory usage increase will be. In other words, they might reduce it by say 15%, but not anywhere near the JIT-less levels, and call it a day. I suppose you always have the option to compile python as --without-jit...
So, you'd accept unladen as the official JIT based on the vague promise of improving its glaring issues sometime in the future? Does that give it the right to be in a "blessed" repo?
I propose my own python implementation for acceptance into the source tree. Right now, it's a single empty file (but I've got lots of ideas!). I'll even consider it a blocking issue if it achieves less than 10x speedup using half as much memory.
Extra memory means a longer start-up time (for small apps) ala JVM, and makes hosting much more expensive. Lots of web hosts are memory / IO bound, not CPU bound. And you are sacrificing memcache size for python speed if you increase python's footprint - not always a winner.
The performance increase is still notable though - I would like to see that static LLVM link changed; I like python for its size, speed, and expressiveness.
I think that a JIT compiler will eventually be added to python, so the sooner this happens the better. The new generation of javascript engines (e.g. V8) have shown us how fast dynamic code can be; there is no reason python can't achieve this either. I also think the swallow team has gone about this in the right way: presenting what they've done, and asking for what needs to happen before it can become mainline. They obviously value this merge, so kudos to google.
On the other hand, performance so far is quite underwhelming. Certainly, as a PEP, this is by no means intended to be merged now, but to provide a roadmap for the future. Here's to hoping they can remove their remaining roadblocks.
"... and a pony" is just an admission that you've already asked a lot and it might not happen. A pony is the kind of thing a child requests on a whim, who is then crushed because they don't understand how ridiculously impractical it would be.
If it was at terminal velocity it should be considered, but it's yet to get off the ground.
Until then, psyco is a great JIT compiler that really works.
Performance goals have not been met so far; it increases memory usage; PyPy is an alternative with more community support (if only because the typical Python programmer knows more Python than C++); and it makes the code much more complex, introducing lots of hard-to-debug problems, at a time when the developers already have trouble getting people to migrate to 3.x.
The 3.x branch does not need a reputation for instability.
(None of this is to say Unladen Swallow is a bad idea, or should be killed; but it should prove its worth first.)