This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: allow python to build for macosx-11.0-arm64
Type: enhancement Stage: resolved
Components: Interpreter Core Versions: Python 3.10, Python 3.9
Status: closed Resolution: duplicate
Dependencies: Superseder: Support macOS 11 and Apple Silicon Macs
View: 41100
Assigned To: Nosy List: corona10, lawrence-danna-apple, ned.deily, ronaldoussoren
Priority: normal Keywords: patch

Created on 2020-06-29 23:57 by lawrence-danna-apple, last changed 2022-04-11 14:59 by admin. This issue is now closed.

File name Uploaded Description Edit
0001-arm64.patch lawrence-danna-apple, 2020-06-29 23:57
Pull Requests
URL Status Linked Edit
PR 21224 closed lawrence-danna-apple, 2020-06-29 23:59
Messages (6)
msg372641 - (view) Author: Lawrence D'Anna (lawrence-danna-apple) * Date: 2020-06-29 23:57
allow python to build for macosx-11.0-arm64, by adding the appropriate case to
msg372647 - (view) Author: Dong-hee Na (corona10) * (Python committer) Date: 2020-06-30 03:50
Thanks, Lawrence for the patch.

I am happy to see the patch from the Apple team.
By the way, is there any way to check that the CPython team can check all the tests works well on the ARM macOS?
msg372648 - (view) Author: Lawrence D'Anna (lawrence-danna-apple) * Date: 2020-06-30 04:03
The tests do not all pass yet, I thought I'd try with the tiny patch to enable building on arm and follow up with more after I getting feedback.

If you prefer, I can wait until I have a complete patch that addresses all test failures on arm, but if you want to do it that way I think it will have to wait until the next seed of Mac OS 11 comes out.

If you want to test it yourself on an arm Mac, we have Developer Transition Kits that include an arm Mac mini
msg372649 - (view) Author: Ned Deily (ned.deily) * (Python committer) Date: 2020-06-30 04:25
Lawrence, thanks for the PR. We appreciate any insights from you all. We ahve already started to build using the first seed of Big Sur and have already committed some fixes. Rather than having multiple open issues covering the same topic, I'd like to suggest that we use the existing one Issue41100 to consolidate the PRs; to that end, I've changed the title of your PR (PR 21224) to reference that issue and I'm going to close this one. I'll add you to the other issue and we can continue discussions. BTW, I believe a DTK is in Ronald's future :)
msg372651 - (view) Author: Lawrence D'Anna (lawrence-danna-apple) * Date: 2020-06-30 04:28
sound good, thanks
msg372676 - (view) Author: Ronald Oussoren (ronaldoussoren) * (Python committer) Date: 2020-06-30 09:39
FYI I have as of a couple of minutes ago received a developer transition kit and can, and will, test on the new hardware.
Date User Action Args
2022-04-11 14:59:33adminsetgithub: 85336
2020-06-30 09:39:32ronaldoussorensetmessages: + msg372676
2020-06-30 04:28:21lawrence-danna-applesetmessages: + msg372651
2020-06-30 04:25:34ned.deilysetstatus: open -> closed

superseder: Support macOS 11 and Apple Silicon Macs

nosy: + ned.deily
messages: + msg372649
resolution: duplicate
stage: patch review -> resolved
2020-06-30 04:03:02lawrence-danna-applesetmessages: + msg372648
2020-06-30 03:50:48corona10setversions: + Python 3.10
2020-06-30 03:50:27corona10setnosy: + ronaldoussoren, corona10
messages: + msg372647
2020-06-29 23:59:14lawrence-danna-applesetstage: patch review
pull_requests: + pull_request20376
2020-06-29 23:57:08lawrence-danna-applecreate