I don't know what's the issue. PyPy shouldn't have breaking changes. They're targeting Python 2.7.x which is a frozen specification.
In the unlikely case that a new release causes code that worked in a previous release to fail, it's simply exposing a bug in either the new or old release.
seems to me that they just released updates bringing it in alignment with python 3.6, which is only one version behind current, no? I'm curious why they couldn't run the pure python implementations through PyPy to test...
why is PyPy not just skipping current Python 3.6 effort and goes directly to 3.7 or at least doing that once in a while (skipping in between versions) ?
Well, the fact that they're running it in PyPy makes all of this that much more challenging to debug - you'd have to look at the runtime-generated bytecode to identify the actual causes.
According to the footnote he tested with pypy 1.9. There was just a post here a day or two ago that pypy 2.3.1 was release. Seems like one should at least use the latest version when testing. Pypy 1.9 was release 2 years ago.
What is stopping PyPy from getting more widespread adoption in the Python community? Surely it isn't that everyone is using the latest version of CPython; it's been years and many are still using 2.7.
In the unlikely case that a new release causes code that worked in a previous release to fail, it's simply exposing a bug in either the new or old release.
reply