PyPy v7.3.1: release of 2.7 and 3.6¶
The PyPy team is proud to release the version 7.3.1 of PyPy, which includes two different interpreters:
- PyPy2.7, which is an interpreter supporting the syntax and the features of Python 2.7 including the stdlib for CPython 2.7.13
- PyPy3.6: which is an interpreter supporting the syntax and the features of Python 3.6, including the stdlib for CPython 3.6.9.
The interpreters are based on much the same codebase, thus the multiple release. This is a micro release, no APIs have changed since the 7.3.0 release in December, but read on to find out what is new.
Conda Forge now supports PyPy as a python interpreter. The support right now is being built out. After this release, many more c-extension-based packages can be successfully built and uploaded. This is the result of a lot of hard work and good will on the part of the Conda Forge team. A big shout out to them for taking this on.
We have worked with the python packaging group to support tooling around
building third party packages for python, so this release updates the pip and
setuptools installed when executing
pypy -mensurepip to
completes the work done to update the PEP 425 python tag from
mean “PyPy 7.3 running python3” to
pp36 meaning “PyPy running python
3.6” (the format is recommended in the PEP). The tag itself was
changed in 7.3.0, but older pip versions build their own tag without querying
pypy. This means that wheels built for the previous tag format will not be
discovered by pip from this version, so library authors should update their
PyPY-specific wheels on PyPI.
The CFFI backend has been updated to version 14.0. We recommend using CFFI
rather than c-extensions to interact with C, and using cppyy for performant
wrapping of C++ code for Python. The
cppyy backend has been enabled
experimentally for win32, try it out and let use know how it works.
cppyy requires a more modern C compiler, so win32 is now built
with MSVC160 (Visual Studio 2019). This is true for PyPy 3.6 as well as for 2.7.
We have improved warmup time by up to 20%, performance of
match if not be faster than CPython, and improved JIT code generation for
generators (and generator expressions in particular) when passing them to
map that consume them.
As always, this release fixed several issues and bugs raised by the growing community of PyPy users. We strongly recommend updating. Many of the fixes are the direct result of end-user bug reports, so please continue reporting issues as they crop up.
You can find links to download the v7.3.1 releases here:
We would like to thank our donors for the continued support of the PyPy project. If PyPy is not quite good enough for your needs, we are available for direct consulting work.
We would also like to thank our contributors and encourage new people to join the project. PyPy has many layers and we need help with all of them: PyPy and RPython documentation improvements, tweaking popular modules to run on pypy, or general help with making RPython’s JIT even better. Since the previous release, we have accepted contributions from 13 new contributors, thanks for pitching in.
If you are a python library maintainer and use c-extensions, please consider making a cffi / cppyy version of your library that would be performant on PyPy. In any case both cibuildwheel and the multibuild system support building wheels for PyPy wheels.
What is PyPy?¶
PyPy is a very compliant Python interpreter, almost a drop-in replacement for CPython 2.7, 3.6, and soon 3.7. It’s fast (PyPy and CPython 2.7.x performance comparison) due to its integrated tracing JIT compiler.
We also welcome developers of other dynamic languages to see what RPython can do for them.
This PyPy release supports:
- x86 machines on most common operating systems (Linux 32/64 bits, Mac OS X 64 bits, Windows 32 bits, OpenBSD, FreeBSD)
- big- and little-endian variants of PPC64 running Linux,
- s390x running Linux
- 64-bit ARM machines running Linux.
Unfortunately at the moment of writing our ARM32 buildbots are out of service, so for now we are not releasing any binaries for that architecture, although PyPy does support ARM 32 bit processors.
Python 3.6 only¶
- Fix for CPython 30891: deadlock import detection causes deadlocks
- Don’t swallow the UnicodeDecodeError in one corner case (fixes issue 3132)
- Follow CPython’s behaviour more closely in sqlite3
- Fix issue 3136: On windows,
os.putenv()cannot have a key with
- More closely follow CPython’s line number output in disassembly of constants
- Don’t give a new error message if metaclass is actually type
fcntl’s handling of errors in functions that do not retry
BUILD_LIST_FROM_ARGas a fast path
- Fix issue 3159:
venvshould copy directories, not just files
- Add missing
- Fix for path-as-
- Fix issue 3166: Obscure ordering-of-which-error-to-report-first
- Improve the performance of
str.join. This helps both lists (in some situations) and iterators, but the latter is helped more. Some speedups of >50% when using some other iterator
os.environduring startup on Darwin