Ned Deily <n...@python.org> added the comment:

The short answer to the original issue: at the moment, build-installer.py 
continues to create python.org installers in the legacy bundle installer format 
that is no longer supported by more modern versions of macOS and there are 
additional steps that are used to convert the artifacts produced by 
build-installer.py into a modern flat-package (.pkg) format installer. Those 
steps are outlined in Mac/BuildScript/README.rst but the exact commands are not 
provided there. The longer answer is that we have long provided macOS 
installers that are designed to work on a very wide range of macOS versions and 
Mac hardware. Up until very recently, the production of an installer required 
multiple steps on different versions of macOS to be able to meet those 
requirements, i.e. the build of Python itself had to run on an older system 
(macOS 10.9) but the flat package and signing has to run on a more recent 
system to be able to be notarized by Apple. And that manufacturing has evolved 
over many years 
 as Apple has attempted to enhance macOS security while minimizing the impact 
on end users (e.g. Gatekeeper, code signing, notarization). As of fairly 
recently (Python 3.10.1 et al) with the addition to Python of full 
"weaklinking" support on macOS (along with Apple Silicon and Big Sur support), 
it is now possible to build on a current system while supporting older systems 
as well as we now do in the new universal2 installer variant. Since we are 
still providing the legacy 10.9 Intel-only installer variant for 3.9.x 
releases, there hasn't been an urgent need to modify the overall manufacturing 
process yet, but I do plan to do so and document prior to the upcoming 3.11 
feature code cutoff (in part to better support Apple Silicon Macs).

----------
assignee:  -> ned.deily

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue46548>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to