On Wed, Nov 4, 2026 at 8:31 PM matti picus via NumPy-Discussion <
[email protected]> wrote:

> Recently PyPy release a version 3.12 interpreter. This puts NumPy in a
> strange situation. PyPy 3.11 was Tier 2 until NumPy dropped python3.11
> in version 2.4. Then PyPy (and CPython) 3.11 were dropped for NumPy
> 2.5. Now we are a few weeks before NumPy 2.6, which will be the last
> version to support 3.12. I propose that NumPy release PyPy 3.12
> wheels, restoring it to Tier 2, for the 2.6 release, and then drop it
> together with CPython 3.12 after, again removing PyPy from the Tier 2
> support. I am willing to be the support contact for this platform.
> This will add 5 new wheels (manylinux_x86_64, manylinux_aarch64,
> macos-arm64, macos-x86_64, and win-amd64 ), since PyPy does not
> support win-arm64. In table form:
>
> NumPy version   PyPy Tier 2 support
> 2.4                         3.11
> 2.5                        None  (NEP57 current status)
> 2.6                         3.12  (this proposal)
> 2.7                        None, unless PyPy releases a 3.13 by May 2027.
>

This plan seems reasonable to me. The main reasons I'm +1 is that there's
still demand for PyPy, and that Matti as a lead maintainer of both NumPy
and PyPy will ensure that this stays in good shape (or gets removed again).

It would be good to hear about the Limited C API support plans for PyPy.
You were working on that, right Matti? As a more niche target, it'd be good
if it were possible to transition PyPy wheels to the Stable ABI.

Cheers,
Ralf



>
> Thanks
> Matti
> _______________________________________________
> NumPy-Discussion mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mailman3//lists/numpy-discussion.python.org
> Member address: [email protected]
>
_______________________________________________
NumPy-Discussion mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3//lists/numpy-discussion.python.org
Member address: [email protected]

Reply via email to