Add pip wheel build constraints to fix numpy builds #133962
Merged
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.
Proposed change
For each of the last two numpy releases we had issues with the wheel build. Those were caused by ninja
1.11.1.2
which is part of the build system. They should have been resolved with1.11.1.3
but at least forarmhf
the issue seems to still persists. scikit-build/ninja-python-distributions#274This PR attempts to fix the issue for us by adding an additional constraints file to be used during wheel build and pinning the known good version
1.11.1.1
.For constraints to be considered during the creation of isolated build environments, they need to be passed via the env variable
PIP_CONSTRAINT
./CC @bdraco
Type of change
Additional information
Checklist
ruff format homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
.To help with the load of incoming pull requests: