mach: Force the use of arm64 Python when running with Windows on arm64#42371
Merged
jdm merged 1 commit intoservo:mainfrom Feb 6, 2026
Merged
mach: Force the use of arm64 Python when running with Windows on arm64#42371jdm merged 1 commit intoservo:mainfrom
jdm merged 1 commit intoservo:mainfrom
Conversation
servo-highfive
added
the
S-awaiting-review
Signed-off-by: Daniel Paoliello <[email protected]>
mrobinson
changed the title
servo-highfive
removed
the
S-awaiting-review
servo-highfive
added
the
S-awaiting-merge
yezhizhen
approved these changes
Feb 6, 2026
servo-highfive
removed
the
S-awaiting-merge
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
4 participants
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.
There is currently a bug in UV that results in it using the x64 flavor of Python when running on Arm64 Windows. This then causes all Python scripts to believe they are on an x64 device and so Server installs the wrong dependencies and builds for the wrong architecture.
Testing: Local on my Arm64 Windows device
Contributes to fixing #40611