Repository navigation
ci: Skip 3.14t wheels on 32-bit Linux - #800
Merged
Merged
Conversation
rust-numpy 0.30, pulled in through pyo3-arrow by the pyo3 0.30 bump, refuses to compile free-threaded Python before 3.15 on 32-bit targets. This broke the armv7 (and would break the x86) Linux wheel builds for py-v0.12.0. Free-threaded Python 3.15+ on these targets is still covered by the abi3t-py315 wheels. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR was written by Claude (Claude Code), not by @kylebarron.
The
py-v0.12.0wheel build failed on thearmv7Linux targets (manylinux and musllinux) while buildingcp314t:#798 bumped
numpyfrom 0.29 to 0.30;pyo3-arrowalways depends on it. numpy 0.30 (PyO3/rust-numpy#556) adds thiscompile_error!because a NumPy struct-alignment bug in free-threaded builds on 32-bit platforms is only fixed for Python 3.15+. Thex86(i686) jobs were cancelled before they reached that step, but they're also 32-bit and would fail the same way.Change
extra-interpreterslist, the same pattern the Windows job uses since ci: add Windows ARM64 wheels #775.x86andarmv7build onlypypy3.11. All 64-bit targets still build3.14tandpypy3.11.As a result, 0.12.0 won't ship
cp314twheels for 32-bit Linux. Free-threaded Python 3.15+ on those platforms is still covered by theabi3t-py315wheels, which built fine onarmv7in the failed run.Testing
actionlintpasses.workflow_dispatch(it doesn't publish): https://github.com/developmentseed/obstore/actions/runs/38765919628After merging
To unblock the 0.12.0 release, move the
py-v0.12.0tag to the merge commit and force-push it. That re-runs the build and publishes to PyPI, the same way 0.11.0 was released after #741.🤖 Written by Claude Code