-
-
Notifications
You must be signed in to change notification settings - Fork 54
Description
Context: I'm trying to apply the following patch to my dependency specs
- pyo3 = { version = "0.25.1", features = ["extension-module", "abi3-py310"] }
+ pyo3 = { version = "0.25.1", features = ["extension-module", "abi3"] }with the goal of allowing my users to build from source and select their own minimum Python version (Python 3.10 is the absolute minimum, but nothing prevents building a cp313-abi3 wheel).
This is made possible with maturin>=1.8.6, thanks to PyO3/maturin#2597, and it works as excepted when building locally.
However, I find that this breaks building my own wheels in CI through maturin-action. Specifically, the containerized maturin does a poor job at guessing which interpreter should be used. As far as I understand, the solution should be to add args: -i python3.10. However, I find that this selects Pypy3.10 (as seen for instance in https://github.com/neutrinoceros/rlic/actions/runs/16424717268/job/46412012510). Meanwhile, cpython3.10 or 3.10 do not seem to be valid inputs for the -i/--interpreter flag in maturin build and friends, so I couldn't find a workaround.
Am I doing something wrong or is this a bug ?