pyo3 ci: Add 3.15 in CI

Oct 15 '25 15:10 clin1234

I added full build, if you want to fixup merge conflict we can see what initial results are.

Oct 16 '25 11:10 davidhewitt

You should bump cpython’s max-version in pyo3-ffi/cargo.toml to 1.15.

Oct 21 '25 07:10 bschoenmaeckers

You should bump cpython’s max-version in pyo3-ffi/cargo.toml to 1.15.

cpython 3.15 C-API is I think still moving, wouldn't it better to keep the error message and use UNSAFE_PYO3_SKIP_VERSION_CHECK until the API is stabilized? I am a bit afraid we ship a PyO3 version that end up broken on cpython 3.15 released versions

Oct 22 '25 07:10 Tpt

You should bump cpython’s max-version in pyo3-ffi/cargo.toml to 1.15.

cpython 3.15 C-API is I think still moving, wouldn't it better to keep the error message and use UNSAFE_PYO3_SKIP_VERSION_CHECK until the API is stabilized? I am a bit afraid we ship a PyO3 version that end up broken on cpython 3.15 released versions

Agreed, we should not declare support for 3.15 properly until 3.15 is in beta.

In https://github.com/PyO3/pyo3/issues/5093#issue-3019758272 I wrote some thoughts about maybe how we could support 3.15 for development.

Nov 01 '25 14:11 davidhewitt