News for hackers. Stuff that matters.

A comment on PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More. Parent comment

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by upofadown on Thursday October 29, 2015 @09:46AM (#10470914)
The value of PyPy is that it is a thing you can just drop in to make your code faster. If PyPy wants to gain any traction they pretty much have to concentrate on the version with the most existing code.
[ Parent | on HN ]
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by baq on Thursday October 29, 2015 @09:59AM (#10470998)
most of my existing production code is 3.4, hence my question.
[ Parent | on HN ]
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by StavrosK on Thursday October 29, 2015 @01:14PM (#10472613)
I'm/we are also moving everything to 3.4, since we want all the nice things.
[ Parent | on HN ]
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by ciupicri on Thursday October 29, 2015 @12:43PM (#10472372)
Python 3 is the future. There's a chance that when Pypy finally catches up with Python 2.7 (numpy, C extensions etc), it will be obsolete.
[ Parent | on HN ]
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by upofadown on Thursday October 29, 2015 @04:35PM (#10474082)
Python3 is a language. Python2 is also a language. Python3 might someday become wildly popular, but that doesn't magically make Python2 go away just because the name sounds the same.
[ Parent | on HN ]
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by ciupicri on Thursday October 29, 2015 @07:23PM (#10475173)
From [PEP 373]:

> The End Of Life date (EOL, sunset date) for Python 2.7 has been moved five years into the future, to 2020. This decision was made to clarify the status of Python 2.7 and relieve worries for those users who cannot yet migrate to Python 3. See also PEP 466.

> This declaration does not guarantee that bugfix releases will be made on a regular basis, but it should enable volunteers who want to contribute bugfixes for Python 2.7 and it should satisfy vendors who still have to support Python 2 for years to come.

> There will be no Python 2.8 (see PEP 404).

Take note that the initial date was set to 2015 [2] and it was delayed only last year.

   [PEP 373]: http://legacy.python.org/dev/peps/pep-0373/
   [2]: https://hg.python.org/peps/rev/76d43e52d978
[ Parent | on HN ]