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 gregneagle
Recipients gregneagle, ned.deily, ronaldoussoren
Date 2020-11-30.18:28:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1606760917.9.0.450918621788.issue42514@roundup.psfhosted.org>
In-reply-to
Content
The current Python.framework installed by the macOS packages is hard-coded to /Library/Frameworks/Python.framework and breaks if renamed or moved.

A relocatable framework would allow users/admins/developers to install a specific framework to an alternate location, or include it inside an application bundle, or access it from a mounted disk image.

Currently it is possible to use `otool` and `install_name_tool` to convert the current framework into one that can be relocated, but doing so breaks any code signing. With Apple Silicon, all executable code and libraries must be code signed, so the effort of relocating the Python framework becomes that more difficult.

Ideally the official macOS framework would be built as relocatable, eliminating the need to modify it and re-sign it to use it anywhere other than  /Library/Frameworks/Python.framework.
History
Date User Action Args
2020-11-30 18:28:37gregneaglesetrecipients: + gregneagle, ronaldoussoren, ned.deily
2020-11-30 18:28:37gregneaglesetmessageid: <1606760917.9.0.450918621788.issue42514@roundup.psfhosted.org>
2020-11-30 18:28:37gregneaglelinkissue42514 messages
2020-11-30 18:28:37gregneaglecreate