Skip to content

🤖 feat!: support Python 3.11–3.15, drop 3.10 - #58

Merged
dancergraham merged 4 commits into
mainfrom
ci/python-3.11-3.15
Nov 16, 2026
Merged

dancergraham merged 4 commits into
mainfrom
ci/python-3.11-3.15

Conversation

@dancergraham

@dancergraham dancergraham commented Nov 16, 2026 •

Copy link
Copy Markdown
Owner

Brings CI and packaging in line with the Python versions currently supported upstream: 3.11 to 3.15. 3.10 reached end of life on 2026-10-01, and 3.15.0 is out.

Breaking change for users: requires-python goes from >=3.10 to >=3.11, and no cp310 wheels will be published from the next release. Existing releases stay installable on 3.10. Consider a minor version bump for the release that includes this.

Changes

  • pyo3 0.28.3 → 0.30.1, numpy crate 0.28.0 → 0.30.0. 0.30.0 adds Python 3.15 support. No source changes were needed.
  • CI:
    • The pytest matrix is now 3.11–3.15.
    • Windows and macOS install 3.11–3.15, so --find-interpreter builds a wheel for each. Before, they only set up 3.14, and Windows x86 built only cp314.
    • Removed PYO3_USE_ABI3_FORWARD_COMPATIBILITY. pyo3 0.30 doesn't need it, and leaving it in would hide a future unsupported interpreter.
    • The Linux aarch64 test now uses ubuntu24.04 with a venv. ubuntu22.04 ships Python 3.10, which would no longer have a matching wheel.
    • The 32-bit Linux (i686) builds now list their interpreters explicitly. rust-numpy 0.30 refuses to compile free-threaded 3.14t on 32-bit ("only supported from 3.15+"), so cp314t i686 wheels are no longer published. cp315t i686 still builds.
  • Rebased onto main after 🤖 ci: harden workflow per zizmor audit #56 and 🤖 ci: add rustfmt and clippy lint gate #57. The SHA pins and the tag-aware sccache setting are kept.

Verified

  • Locally (macOS arm64):
    • cargo clippy --all-targets -- -D warnings is clean on pyo3 0.30.
    • pytest passes 16/16 on Python 3.15.0 and on 3.11.17.
  • CI: all jobs pass, including the lint job from 🤖 ci: add rustfmt and clippy lint gate #57.
  • Wheel artifacts: I downloaded them from run 43934915743 and checked every platform. Each has cp311–cp315, and there's no cp310 anywhere:
platform wheels
macosx arm64 cp311–cp315, cp315t
manylinux x86_64 cp311–cp315, cp314t, cp315t, pp311
manylinux aarch64 cp311–cp315, cp314t, cp315t, pp311, pp312
manylinux i686 cp311–cp315, cp315t, pp311
musllinux x86_64 / aarch64 cp311–cp315, cp314t, cp315t, pp311, pp312
musllinux i686 cp311–cp315, cp315t, pp311, pp312
win_amd64 / win32 cp311–cp315

Not addressed

The i686 wheels are still untested. numpy publishes no i686 Linux wheels, so installing them means building numpy from source.

🤖 Generated with Claude Code

dancergraham and others added 4 commits November 16, 2026 20:00
pyo3 0.30.0 adds support for Python 3.15.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Python 3.10 reached end of life on 2026-10-01. maturin's
--find-interpreter respects requires-python, so cp310 wheels are no
longer built.

BREAKING CHANGE: Python 3.10 is no longer supported.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- pytest matrix: 3.11-3.15
- Windows and macOS: install 3.11-3.15 so --find-interpreter builds a
  wheel for each
- drop PYO3_USE_ABI3_FORWARD_COMPATIBILITY, which pyo3 0.30 no longer
  needs and which would hide a missing interpreter version
- Linux aarch64 test: ubuntu22.04 ships Python 3.10, which no longer
  has a wheel; use ubuntu24.04 and a venv (PEP 668)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
rust-numpy 0.30 fails to compile for free-threaded Python 3.14 on 32-bit
targets ("free-threaded Python on 32bit platforms is only supported from
3.15+"). List interpreters explicitly for the i686 manylinux and
musllinux builds, keeping every other interpreter --find-interpreter
picked up there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@dancergraham
dancergraham marked this pull request as ready for review November 16, 2026 19:13
@dancergraham
dancergraham merged commit 2f7eff2 into main Nov 16, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant