from Hacker News

PyPy v5.9 Released

by mdf on 10/5/17, 1:36 PM with 48 comments

• by syllogism on 10/5/17, 10:49 PM

  This is amazing -- we have a small mountain of Cython code, and almost everything is working out of the box!

  Tests failing:

  * https://github.com/explosion/spaCy

  Confirmed working:

  * https://github.com/explosion/thinc

  * https://github.com/explosion/preshed

  * https://github.com/explosion/cymem

  * https://github.com/explosion/murmurhash

  I doubt spaCy will ever be faster on PyPy (the neural network library Thinc is currently 50% slower). It'd still be really great to get it running, so people who benefit from PyPy for other parts of their stack don't have to manage two Python environments.

• by theli0nheart on 10/5/17, 3:30 PM

  This is great. Can't wait until Python 3.5 support is out of beta.

  Just out of curiosity, I'd love to hear from others who've used PyPy for their web apps. Are there any issues to look out for? I remember that a few years ago, packages like psycopg2 were not compatible, which made the migration somewhat difficult. Would love to hear real-world experiences here.

• by mattip on 10/5/17, 3:50 PM

  The original title emphasises that NumPy and Pandas now are functional on PyPy.

  The PyPy JIT cannot look inside C code, and crossing the python-c interface is slow, but give it a chance and you may be pleasantly surprised how fast your pure python code can run.

• by SEJeff on 10/5/17, 4:07 PM

  I wonder if this will run apistar: https://github.com/encode/apistar which is currently the fastest (python 3.6 generally) python web framework out there.

• by haikuginger on 10/5/17, 4:26 PM

  As I do with every PyPy release, I would like to point out that the PyPy official benchmarks for comparison against CPython[0] continue to misleadingly compare their latest and greatest with CPython 2.7.2 (released in 2011), as opposed to the modern CPython 2.7.13 or 3.5.3 versions for which they target API compatibility.

  [0]http://speed.pypy.org

• by babataiyoh on 10/6/17, 3:09 AM

  Is there a list of well-known c-extensions for which PyPy is known to work or for which there are well-maintained cpyext ports ?

  Update: found it at https://bitbucket.org/pypy/compatibility/wiki/Home

• by hyperbovine on 10/5/17, 3:52 PM

  Was surprised to see Cython support on this list. Can somebody elaborate on the relationship between the two? I had always viewed them as alternatives.

• by gkya on 10/5/17, 5:26 PM

  Is PyPy ideally plug'n'play, i.e. is it supposed to be able to seamlessly replace the CPython interpreter (ideally in that it may not factually be completely compatible, but is it aimed to be completely compatible)?

• by avyfain on 10/5/17, 10:09 PM

  Thanks @fijal and team for all the effort! This is awesome.

  The last update on the Pypy+Pandas wiki[0] is from this August, and it mentions that there are still 15 outstanding failing tests. Does this release mean that 5.9 is now at 100% parity? What does the same metric look like for Pypy+Numpy, and where can that one be tracked if not 100% yet?

  I am looking forward to migrating some pipelines over to 5.9 soon.

  [0] https://bitbucket.org/pypy/pypy/wiki/cpyext_2_-_cython_and_p...

• by howfun on 10/5/17, 2:09 PM

  I am glad to hear it!