PEP 3146: Merge Unladen Swallow into CPython
svn.python.org
PEP 3146: Merge Unladen Swallow into CPython
1–10 of 34 posts
Re: PEP 3146: Merge Unladen Swallow into CPython
#2A pretty, rendered version of the markup is available here: http://www.python.org/dev/peps/pep-3146/
Re: PEP 3146: Merge Unladen Swallow into CPython
#3I want a pony from Guido too
Re: PEP 3146: Merge Unladen Swallow into CPython
#4I want a pony from Guido too
Surprisingly on-topic :-) For the curious, the reference is within this article:
"We seek the following from the BDFL:
Approval for the overall concept of adding a just-in-time compiler to CPython, following the design laid out below.
Permission to continue working on the just-in-time compiler in the CPython source tree.
Permission to eventually merge the just-in-time compiler into the py3k branch once all blocking issues have been addressed.
A pony."
Re: PEP 3146: Merge Unladen Swallow into CPython
#5I want a pony from Guido too
Guido doesn't want to share the pony: http://farm4.static.flickr.com/3569/3401670115_54e1d32200.jp...
Re: PEP 3146: Merge Unladen Swallow into CPython
#6It's unfortunate that they never hit their original 5x performance boost. Hopefully acceptance into CPython will help.
Re: PEP 3146: Merge Unladen Swallow into CPython
#7It's unfortunate that they never hit their original 5x performance boost. Hopefully acceptance into CPython will help.
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.
Re: PEP 3146: Merge Unladen Swallow into CPython
#8It's unfortunate that they never hit their original 5x performance boost. Hopefully acceptance into CPython will help.
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".
Re: PEP 3146: Merge Unladen Swallow into CPython
#9I 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.
Re: PEP 3146: Merge Unladen Swallow into CPython
#10...African or European?