Any Release incoming for pypy 3.x?
I am waiting to switch to Python3 , but i am not switching without pypy3 moving forward
This year’s GSoC made significant progress towards 3.3 support. There was some talk of releasing that but I’m not sure it’s quite there yet. Are you looking for that specifically or just an updated version of the 3.2 compatible pypy3? It might be time for another release of the 3.2 version with an upgraded cffi among other things from the default branch (which should be less work than finishing 3.3 support). -- Philip Jenvey
Hi, I planned to do a release of the Python 3.2-compatible version after the PyPy 2.6.1 release but didn't have time to do so until recently. But now that the PyPy 4.0.0 release is imminent, it makes sense to wait a week longer and then do a release of the Python 3.2-compatible version based on PyPy 4.0.0. Python 3.3 support is almost complete feature-wise. However, there are still a lot of failing tests which are often a bit subtle to fix. I hope to be able to invest more time in the next weeks. -Manuel On 2015-10-20 21:16, Philip Jenvey wrote:
Thanks a lot. PyPy3 is lagging behind by a lot so i just pinged. PyPy3 users will be particularly interested in 3.4-3.5x due to async-await , yield from and many other powerful features. As tornado now heading towards Python3.5 async-await , these things become quite interesting. On Thu, Oct 22, 2015 at 3:46 AM, Manuel Jacob <me@manueljacob.de> wrote:
Jacob, I think Python 3.5 going to be the version many will be switching , want to know if it is beneficial to jump directly to that? as PyPy3 lacks behind a lot in development vs Python 2 , a skip would be less work? On Thu, Oct 22, 2015 at 3:46 AM, Manuel Jacob <me@manueljacob.de> wrote:
This year’s GSoC made significant progress towards 3.3 support. There was some talk of releasing that but I’m not sure it’s quite there yet. Are you looking for that specifically or just an updated version of the 3.2 compatible pypy3? It might be time for another release of the 3.2 version with an upgraded cffi among other things from the default branch (which should be less work than finishing 3.3 support). -- Philip Jenvey
Hi, I planned to do a release of the Python 3.2-compatible version after the PyPy 2.6.1 release but didn't have time to do so until recently. But now that the PyPy 4.0.0 release is imminent, it makes sense to wait a week longer and then do a release of the Python 3.2-compatible version based on PyPy 4.0.0. Python 3.3 support is almost complete feature-wise. However, there are still a lot of failing tests which are often a bit subtle to fix. I hope to be able to invest more time in the next weeks. -Manuel On 2015-10-20 21:16, Philip Jenvey wrote:
Thanks a lot. PyPy3 is lagging behind by a lot so i just pinged. PyPy3 users will be particularly interested in 3.4-3.5x due to async-await , yield from and many other powerful features. As tornado now heading towards Python3.5 async-await , these things become quite interesting. On Thu, Oct 22, 2015 at 3:46 AM, Manuel Jacob <me@manueljacob.de> wrote:
Jacob, I think Python 3.5 going to be the version many will be switching , want to know if it is beneficial to jump directly to that? as PyPy3 lacks behind a lot in development vs Python 2 , a skip would be less work? On Thu, Oct 22, 2015 at 3:46 AM, Manuel Jacob <me@manueljacob.de> wrote:
participants (3)
-
Manuel Jacob -
Philip Jenvey -
Phyo Arkar