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 hhas
Recipients hhas, ned.deily, ronaldoussoren
Date 2018-06-07.12:18:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1528373916.56.0.592728768989.issue33794@psf.upfronthosting.co.za>
In-reply-to
Content
The Python.framework installed at '/Library/Frameworks/Python.framework' should have a subdirectory structure similar to this:

    Python.framework
    |
    |-Headers [symlink to 'Versions/Current/Headers']
    |
    |-Python [symlink to 'Versions/Current/Python']
    |
    |-Resources [symlink to 'Versions/Current/Resources']
    |
    |-Versions
    | |
    | |-2.7 [directory created by 2.7 installer]
    | |
    | |-3.5 [directory created by 3.5 installer]
    | |
    | |-3.6 [directory created by 3.6 installer]
    | |
    | ...
    | |
    | |- Current [symlink to last installed version, e.g. '3.6']

Current Python.framework installers create a 2.x/3.x directory and Headers+Python+Resources symlinks, but fail to create a 'Current' symlink. This breaks the top-level symlinks and causes importing the framework via NSBundle to fail.

Please fix the framework build and/or install script to create the missing symlink.
History
Date User Action Args
2018-06-07 12:18:36hhassetrecipients: + hhas, ronaldoussoren, ned.deily
2018-06-07 12:18:36hhassetmessageid: <1528373916.56.0.592728768989.issue33794@psf.upfronthosting.co.za>
2018-06-07 12:18:36hhaslinkissue33794 messages
2018-06-07 12:18:36hhascreate