[3.14] GH-134291: Support older macOS deployment targets for JIT builds (GH-137211) #137701
Conversation
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
ned-deily
requested review from
brandtbucher and
savannahostrowski
as code owners
Member
Author
|
There was a minor merge conflict when backporting #137211 so I manually cherry-picked a backport. This should go into 3.14.0rc2 so we and other downstream distributors can build with an older macOS release target. |
hugovk
approved these changes
Aug 13, 2025
github-project-automation
bot
moved this from Todo
to Done
in Release and Deferred blockers 🚫
kumaraditya303
pushed a commit
to miss-islington/cpython
that referenced
this pull request
Sep 9, 2025
…T builds (pythonGH-137211) (python#137701) Co-authored-by: Brandt Bucher <brandtbucher@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This rolls back GH-126196 and adds stricter checks for newer APIs in JIT CI. We don't really need the superpowers of the newer API (rapid flip-flopping permissions on JIT pages) since our JIT doesn't use self-modifying code.
This allows downstream distributors (like
uv, CC @zanieb) to ship the JIT for more users.