Add PyPy 7.3.2 support

It’s a new triple release:

It releases stable pypy2.7 and pypy3.6 but also for the first time it adds pypy3.7 alpha! I’d like to be able to refer to it via pypy3.7.


They should be built automatically when adds them.

We don’t generally support pre-releases on Python.

@webknjaz If it’s alpha, you’re going to get better luck with the branch tip, pypy-dev. It’s currently broken in Pyenv though since the PyPy project has moved.

@BanzaiMan you can check out into cpython-builder's pyenv to get PyPy builds fixed.
You also need to drop the automatic pypy3-dev builds since PyPy has now only one development head, default (checked out by pypy-dev) and the py3k branch is stale and unusable, see

I second this request.

As it is right now, my project ( aio-libs/aiosmtpd ) keeps experiencing failures because the currently provided pypy3 package is 7.1.1-beta0 and it had NOT yet implemented the fix to bpo-27931. We finally just took out the pypy3 job from travis.yml.

PyPy 7.3.1 – the version I have on my computer – has implemented the fix. So PyPy 7.3.2 should also as well.

At the very least, the PyPy3 version on Travis CI should be upgraded to 7.3.1. So no need for supporting “pre-releases”, but already implementing important bugfixes.

EDIT: Huh, just found out that 7.3.1 is already supported and I can specify pypy3.6-7.3.1 to use it. A bit strange why pypy3 is still pointing to 7.1.1-beta0 though…

PyPy 7.3.3 is now out, with these upgrades:

  • PyPy2.7, inc. stdlib of CPython 2.7.13 -> 2.7.18
  • PyPy3.6, inc. stdlib of CPython 3.6.9 -> 3.6.12
  • PyPy3.7, inc. stdlib of CPython 3.7.9, alpha -> beta

We are waiting for

and new ones for 7.3.3 to be made available.