Release/0.50.0 - #953
Merged
Merged
Conversation
Setting PIP_BUILD_CONSTRAINT unconditionally breaks the macOS arm64 build: pip rejects it together with --no-build-isolation (`--build-constraint cannot be used with --no-build-isolation`), which failed the 0.50.0 release bundle on build-macos-wheels (arm64). Set PIP_BUILD_CONSTRAINT only when the GDAL build uses isolation (x86_64 / Linux / Windows); the arm64 --no-build-isolation path is already covered by PIP_CONSTRAINT, which caps its setuptools pre-install. Validated on a bundle dry-run: both macOS jobs green, GDAL built for all Python versions, zero build-constraint / -std=c++11 errors.
|
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
1 participant
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.
Description
Issues
Type of change
Check relevant points.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Provide instructions so we can reproduce.
Please also list any relevant details for your test configuration
Test A
Test B
Checklist: