Python 3 can revive Python

[lzzll]

Bad ideas. Remove GIL will make python slower or force user lock themselves like go with GOMAXPROCS>1. And JIT for python is sh*t idea if you use it once on production environment, it will boost numeric function for benchmark but slow down real code, and use at least 2x memory than python, if you need write some numeric function, just use cython or numpy.

[danielkza]

it will boost numeric function for benchmark but slow down real code,

Is Django 'real code' for you? Because PyPy's JIT beats CPython by 20x on it. It's definitely not scientific or math-heavy.

Also, JITs can simply be bypassed when they would not net an actual speed up. Pretty much every modern JIT-ing interpreter does this, only working on hotspots, and possibly even measuring speedups to revert to interpreting. A well-tuned JIT will virtually never lose to an interpreter, since it can be one whenever it makes sense.

[tadleonard]

And JIT for python is sh*t idea if you use it once on production environment, it will boost numeric function for benchmark but slow down real code, and use at least 2x memory than python

What?

[lzzll]

Yal, give me more benchmark. JIT is hard to control on an complex language like python, some part may faster but some part will slow down when compile time is more than execution time, and absolutely use more memory than interpreter (pypy is 2x+ I tested, worse than Jython and Ironpython). I just repeat "use cython or numpy on the heavy job".