Support for PyPy 3.11

[mattip]

Bug Description

PyPy is working on a 3.11 version. This will require some adaptation from PyO3. I am opening an tracking issue for the C API changes that I think might be relevant.

• right now the version are limited (changing that is easy)
• the PyBUF_MAX_NDIM macro will change to be like CPython: 64
• I am making an effort to adjust the static functions and macros to be more like C.

Steps to Reproduce

I will try to make a branch in my fork and run it in our binary-testing repo to keep the noise down on this repo.

Backtrace

No response

Your operating system and version

ubuntu x86_64 24.04

Your Python version (python --version)

PyPy 3.11

Your Rust version (rustc --version)

rustc 1.75.0

Your PyO3 version

HEAD

How did you install python? Did you use a virtualenv?

From source

Additional Info

Thanks!

[davidhewitt]

Awesome; thanks for helping out with the support. Given that we will have the version check to prevent users building with PyPy 3.11 prematurely, happy to accept patches into this repo whenever to help make your process simpler.

[mgorny]

PyPy3.11 is out for a few days now, and PyO3 support is becoming a blocker for porting.

[mattip]

Support was added in #4760 and should be available by git-installing PyO3 HEAD

[davidhewitt]

#4760 is merged, most likely this will release in #4905 . If there is a strong community need, maybe we can backport this to PyO3 0.23 but please have patience, I have a busy week ahead and expect to struggle to make much progress before March. From March I will have a lot more time for maintenance 😞

Maybe someone else can handle the backport release, if there is an urgent need and someone willing?

[mgorny]

Maybe someone else can handle the backport release, if there is an urgent need and someone willing?

I suppose this isn't a call for some random like me to make a PR backporting the relevant commits to the older branch?

[davidhewitt]

Only if you believe it to be worth your time, help is always welcome.

[mgorny]

Well, given how much time I've already spent patching PyO3 in Gentoo packages, it is definitely worth my time. Plus, it would make it possible for me to give people easy reproducers for PyPy3.11 regressions.

I suppose I should start by making a pull request to backport the change to release-0.23 branch, and then follow the steps up to the PR from https://github.com/PyO3/pyo3/blob/main/Releasing.md? Do you want me to include some other changes, or is that one + ensuring that tests pass fine?

[davidhewitt]

Totally makes sense, thank you. The steps you propose sound good.

I think including #4902 and #4874 (about to merge, a cherry pick of the squashed commits should hopefully apply trivially) would be really appreciated.

CI running ok should be sufficient for pre release testing.

[mgorny]

Okay, thanks. I'll take a look after dinner.