You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the CI workflow that was generated by maturin 1.7.6 for my project autosar-data-py.
I just updated my code to use pyo3-0.23.2, and wanted to publish a new version to pypi.
The CI workflow succeeded on the Macos and Windows platforms, but failed on Linux - Building for CPython >= 3.7 worked correctly on all platforms, since only Linux builds wheels for PyPy.
Do I need to wait for you to make a new release of maturin, or is this supposed to start working immediately?
I saw that you have a github workflow to automatically build a new docker image, but when I just restarted my CI job, it failed again.
Bug Description
I'm using the CI workflow that was generated by maturin 1.7.6 for my project autosar-data-py.
I just updated my code to use pyo3-0.23.2, and wanted to publish a new version to pypi.
The CI workflow succeeded on the Macos and Windows platforms, but failed on Linux - Building for CPython >= 3.7 worked correctly on all platforms, since only Linux builds wheels for PyPy.
You should be able to see the log of the failed run here: musllinux (ubuntu-22.04, aarch64)
Ideally I would like to exclude the "bad" PyPy versions without changing the minimum CPython version.
Your maturin version (
maturin --version
)1.7.6
Your Python version (
python -V
)3.12.7
Your pip version (
pip -V
)unknown - this is a github workflow runner
What bindings you're using
pyo3
Does
cargo build
work?If on windows, have you checked that you aren't accidentally using unix path (those with the forward slash
/
)?Steps to Reproduce
I don't know how to manually build wheels for PyPy, but I could probably restart the github CI workflow.
The text was updated successfully, but these errors were encountered: