# PyPy v7.3.23: release of python 2.7, 3.11, released 2026-xx-xx

Note

> This is a pre-release announcement. When the release actually happens, it

will be announced on the PyPy blog.

Note

Need to add release date

The PyPy team is proud to release version 7.3.23 of PyPy after the previous release on April 26, 2026. This is a bug-fix release that fixes an overeager warning about unused coroutines, and some problems around multiple inheritance in c-extensions.

This version includes a change to the bytecode interpreter to use exception tables instead of dedicated opcodes. Now the PyPy disassembly will be closer to CPython format. So far it does not impact performance.

We also include changes to code generation to use computed gotos and to more aggressively inline the stack checks when entering a `PyFrame`. These do not yet show up as improvements in speed.pypy.org benchmarks, Our venerable benchmarker machine is using gcc5.4.1 (it was set up 10 years ago when that was standard, like our manylinux 2014 buildbot machines) so we are hopeful an update to infrastructure will show the same improvements that we see when running benchmarks on more modern compilers.

The release 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.18+ (the `+` is for backported security updates)

- PyPy3.11, which is an interpreter supporting the syntax and the features of Python 3.11, including the stdlib for CPython 3.11.15.

The interpreters are based on much the same codebase, thus the double release. This is a micro release, all APIs are compatible with the other 7.3 releases.

We recommend updating. You can find links to download the releases here:

> https://pypy.org/download.html

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. If PyPy is helping you out, we would love to hear about it and encourage submissions to our blog via a pull request to https://github.com/pypy/pypy.org

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: bug fixes, PyPy and RPython documentation improvements, or general help with making RPython's JIT even better.

If you are a python library maintainer and use C-extensions, please consider making a HPy / CFFI / cppyy version of your library that would be performant on PyPy. In any case, cibuildwheel supports building wheels for PyPy.

Footnotes

## What is PyPy?

PyPy is a Python interpreter, a drop-in replacement for CPython. It's fast (PyPy and CPython 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.

We provide binary builds for:

- x86 machines on most common operating systems (Linux 32/64 bits, Mac OS 64 bits, Windows 64 bits)

- 64-bit ARM machines running Linux (`aarch64`) and macos (`macos_arm64`).

PyPy supports Windows 32-bit, Linux PPC64 big- and little-endian, Linux ARM 32 bit, RISC-V RV64IMAFD Linux, and s390x Linux but does not release binaries. Please reach out to us if you wish to sponsor binary releases for those platforms. Downstream packagers provide binary builds for debian, Fedora, conda, OpenBSD, FreeBSD, Gentoo, and more.

## Changelog

### For all versions

#### Bugfixes

- Fix a `SystemError` when `OSError` is raised in `gc.dump_rpy_heap` (#5118)

- Fix bug in `inline_short_preamble` (#5462)

#### Speedups and enhancements

- Speed up `int << int -> long` shifts and leave the exponent of `long ** int` as an int

- Detect performance-cluster L2 cache size instead of efficiency on Apple Silicon

- Use computed-goto on GCC/Clang instead of a big switch statement

- Explicitly inline stack checks at the beginning of each `PyFrame`

### Python 2.7

### Python 3.11

#### Bugfixes including missing compatibility with CPython 3.11

- Fix module and name for builtin classes with deeper hierarchies (#5296)

- Remove over-eager warning emitted when `cr_frame` is accessed on a not started coroutine (#5454)

- Fix `typedef.doc` to reject setting it to a `getset` (#5458)

- Fix more `__text_signature__` incompatibilities (#5458)

- Fix module name of `_sqlite3` exceptions to `sqlite3` like CPython

- `datetime:fromisoformat` raises without setting a context in `_datetime.c`, do the same in datetime.py

- Use `exceptiontable` in the bytecode interpreter like CPython does

- Add `_Py_NO_RETURN` to `_Py_FatalErrorFunc`

- Fix `_pypyjson` encoding of int subclasses (#5478)

- Fixing a bug in computation of `tp_basicsize` for mixed python/c-extension types caused a bug in multiple inheritance with c-extension types used in pybind11. More closely follow the logic of CPython (#5481)

- initialize `MultibyteIncrementalDecoder.state` to 0

- detect incomplete decorator input in the parser (#5484)

#### Speedups and enhancements

- Improve the performance of `str.splitlines`

- Restore lost `heapq.merge()` using a linked tournament tree which is slower in CPython but faster in PyPy. The code was lost in an stdlib update and reverted to the CPython version (#5466)