4 ms·
Reading the thread, it seems there's still an intention to roll the JIT into py3k at some point, but the project devs don't have the time and the community does
by cawhitworth 16y ago
Reading the thread, it seems there's still an intention to roll the JIT into py3k at some point, but the project devs don't have the time and the community doesn't seem to have the inclination to take over the work. I think calling it dead might be overstating things slightly.
Or, seeing as this is Python we're talking about: It's not dead, it's just resting.
- ot 16y agoThe thing is, in two years the project was able to deliver only a very small, say 1.2x, speedup, with a noticeable increase of memory (sometimes 3x). Against Python 2.6. I wouldn't be surprised if Python 2.7 is actually faster on some tests. Is it really worth keeping working on it and merging?
- deleted 16y ago[deleted]
- jnoller 16y agoPart of the reason Python 2.7 is faster on some benchmarks is because of the patches the unladen swallow team pushed upstream into core.
- rbanffy 16y ago> It's not dead, it's just resting. And doing what US already did is about equivalent to eating a cow.
- tspiteri 16y agohttp://www.youtube.com/watch?v=npjOSLCR2hE http://www.youtube.com/watch?v=npjOSLCR2hE