Skip to content

Conversation

aignas
Copy link
Collaborator

@aignas aignas commented Aug 30, 2025

This adds the necessary bits for Windows ARM64 support when evaluating
env markers in requirements files and selecting the right wheels in
experimental_index_url.

Related #2276

This adds the necessary bits for Windows ARM64 support when evaluating
env markers in requirements files and selecting the right wheels in
`experimental_index_url`.

Related bazel-contrib#2276
@aignas aignas force-pushed the feat/add-defaults-for-pypi-support-for-windows-arm64 branch from 82c42d3 to c4c9668 Compare August 30, 2025 15:38
@aignas
Copy link
Collaborator Author

aignas commented Aug 30, 2025

We cannot do this because we have tests using the //docs and due to the lack of wheel for markupsafe, we cannot include win_arm64 in the rules_python defaults.

TBH, maybe we should treat this as a bug and fix it.

@aignas aignas marked this pull request as draft August 30, 2025 16:02
@rickeylev
Copy link
Collaborator

Yeah, it's something we should fix.

It should be OK for a requirements file to not support the full set of platforms the entire build does. I can see that situation happening in a larger repo.

@rickeylev
Copy link
Collaborator

Another thought: does this mean if we add a new platform to rules_python's default, downstream user requirements could break? Eek.

@aignas
Copy link
Collaborator Author

aignas commented Aug 31, 2025

I think the best way would be to hardcode windows to only mean windows intel, then for linux and osx, do similar things. The users should really be specifying things explicitly...

Otherwise us adding platforms may break bazel quely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants