Repository navigation
MNT/CI: move cibuildwheel settings to pyproject.toml - #896
Merged
rgommers merged 1 commit intoNov 14, 2026
Merged
Conversation
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.
Following on from #895, this PR moves remaining cibuildwheel settings from the workflow file to
pyproject.toml.This is a bit smaller than I realised, because
CIBW_BUILDandCIBW_ARCHS_*stay in the workflow because they come from the job matrix. However, we can go further if we like by splitting the manylinux and musllinux jobs and usingonly:with the full build identifiers. I like it as-is.Also, Pyodide also picks up the added build verbosity and
PIP_PREFER_BINARYnow, which I think is harmless and mostly useful.