feat: support arbitrary target_settings in our platforms 3/n #2990
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.
With this PR we can support arbitrary target settings instead of just
plain
constraint_values
. We still have custom logic to ensure that allof the tests pass. However, the plan is to remove those tests once we
have simplified the wheel selection mechanisms and the
pkg_aliases
macro. I.e. if we have at most 1 wheel per platform that the
pypi
bzlmod extension passes to the
pkg_aliases
macro, then we can justhave a simple
selects.with_or
where we list out all of the targetplatform values.
This PR may result in us creating more targets but that is the price
that we have to pay if we want to do this incrementally.
Work towards #2747
Work towards #2548
Work towards #260