I've discovered in another issue that official releases are build on old-ish macos.
Is this patch only for self-built python then?
Or is the intention to release arm and x86 packages separately?
Or perhaps to release "classic x86" and "arm+x86" packages?
We're still working on this so we're not quite ready yet to say exactly what will be rolled out with which releases but our intent is to at least provide a universal installer variant that supports macOS 11.0 Big Sur and earlier systems and both Intel-64 and Apple Silicon natively.
I don't have a definitive answer for your question, but my goal is to make it possible to build the official installers on a recent system. That has several advantages: (1) it is required for arm64, (2) you can use new APIs when using a new system, (3) newer compilers generate better code.
I'd personally like to see 1 installer for Python 3.10: x86_64+arm64 for macOS 10.9 or later. I don't know yet what the best path forward is for 3.9 (and possibly 3.8)
And current installers are indeed build on an old system, before this PR the only way to have an installer that works on macOS 10.9 and later is to build using the 10.9 SDK.
From our perspective, the addition of runtime availability checks as part of this change is fantastic. We ship our own custom fork of Python in our macOS app, which we build using the standard/recommended approach: use the latest Xcode and macOS SDK + set your deployment target to the minimum version you want to support at runtime.
ProTip!
Use n and p to navigate between commits in a pull request.
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.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
Learn more.
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
You can always update your selection by clicking Cookie Preferences at the bottom of the page.
For more information, see our Privacy Statement.
Essential cookies
We use essential cookies to perform essential website functions, e.g. they're used to log you in.
Learn more
Always active
Analytics cookies
We use analytics cookies to understand how you use our websites so we can make them better, e.g. they're used to gather information about the pages you visit and how many clicks you need to accomplish a task.
Learn more
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bpo-41100: Support macOS 11 and Apple Silicon #22855
bpo-41100: Support macOS 11 and Apple Silicon #22855
Changes from all commits
919efcc69c39f33940c86deda5f0ea3c200552bca8e0c23a1e637a7702fb660ba2f5a38e3b45487c942b515fbe6eee54373a1d4f22f019f4cec3da786b5cf3d604cefdde0ba47ac26c4191a2d7e6d195bcfb02ba003dae8004ba4e601934654576ab6af77abb653df998af7b3817d9bf8684d9d0b4461036deb9233d5710c3113eb587e53e24ef276e0614bce6478fa3f729495daff996681261b17a3d57e64e95fef2e9324eb0d0296666bFile filter...
Jump to…
dimaqqOct 23, 2020
Contributor
I've discovered in another issue that official releases are build on old-ish macos.
Is this patch only for self-built python then?
Or is the intention to release arm and x86 packages separately?
Or perhaps to release "classic x86" and "arm+x86" packages?
ned-deilyOct 23, 2020
Member
We're still working on this so we're not quite ready yet to say exactly what will be rolled out with which releases but our intent is to at least provide a universal installer variant that supports macOS 11.0 Big Sur and earlier systems and both Intel-64 and Apple Silicon natively.
ronaldoussorenOct 23, 2020
Author
Contributor
I don't have a definitive answer for your question, but my goal is to make it possible to build the official installers on a recent system. That has several advantages: (1) it is required for arm64, (2) you can use new APIs when using a new system, (3) newer compilers generate better code.
I'd personally like to see 1 installer for Python 3.10: x86_64+arm64 for macOS 10.9 or later. I don't know yet what the best path forward is for 3.9 (and possibly 3.8)
And current installers are indeed build on an old system, before this PR the only way to have an installer that works on macOS 10.9 and later is to build using the 10.9 SDK.
maxbelangerOct 23, 2020
Contributor
From our perspective, the addition of runtime availability checks as part of this change is fantastic. We ship our own custom fork of Python in our macOS app, which we build using the standard/recommended approach: use the latest Xcode and macOS SDK + set your deployment target to the minimum version you want to support at runtime.