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.

Author ned.deily
Recipients bettyrab, ned.deily, ronaldoussoren
Date 2021-08-18.04:32:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1629261153.24.0.0371712443527.issue44933@roundup.psfhosted.org>
In-reply-to
Content
The "python3.x-intel64" executable was added for macOS "universal2" builds by Issue44009 in the 3.9.5 and 3.8.10 releases. As described in the issue and the changelog entries, the rationale is:

"Provide “python3.x-intel64” executable to allow reliably forcing macOS universal2 framework builds to run under Rosetta 2 Intel-64 emulation on Apple Silicon Macs. This can be useful for testing or when universal2 wheels are not yet available."

We provided an analogous "python3.x-32" executable for macOS "intel" (x64_64 and i386 archs) builds for a similar reason.

Although it is mentioned in the changelog (and the python.org macOS installer ReadMe), I didn't anticipate that there would be anyone attempting to build and submit a universal binary for Apple notarization and who would be affected by this change: sorry about that! You can just either add the new executable to your codesigning script or you could delete the file before codesigning if you don't have a need to provide it to your users: it isn't needed unless you want to reliably force running under Rosetta 2 Intel emulation on an Apple Silcon Mac.
History
Date User Action Args
2021-08-18 04:32:33ned.deilysetrecipients: + ned.deily, ronaldoussoren, bettyrab
2021-08-18 04:32:33ned.deilysetmessageid: <1629261153.24.0.0371712443527.issue44933@roundup.psfhosted.org>
2021-08-18 04:32:33ned.deilylinkissue44933 messages
2021-08-18 04:32:33ned.deilycreate