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 KevinPackard, ned.deily, ronaldoussoren
Date 2019-10-01.03:29:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thanks for the reminder.  Unfortunately, the macOS installer is working as designed.  As discussed at length in Issue18117 (and elsewhere), building using the -framework Python, either directly in compiler calls or indirectly through Xcode is problematic because Python installers install all versions, 2.x and 3.x, into the same framework location, /Library/Frameworks/Python.framework.  Since it was common especially in the early days of Python 3 to install both Python 2 and Python 3, the decision was made to only have Python 2.x installs add or modify the Current symlink.  As also noted, it was probably a mistake back then to not install Python 3.x versions to a differently-names framework so you can be sure whether you are attempting to link with Python 2 or Python 3 but that ship has sailed.  However now that Python 2 is about to enter end-of-life, we should reconsider that behavior.

In the meantime, there should be a simple workaround: just create the symlink yourself after installing a new Python 3.x version.  So something like:

sudo sh
umask 022
cd /Library/Frameworks/Python.framework/Versions
rm -f Current
ln -s 3.7 Current
Date User Action Args
2019-10-01 03:29:25ned.deilysetrecipients: + ned.deily, ronaldoussoren, KevinPackard
2019-10-01 03:29:25ned.deilysetmessageid: <>
2019-10-01 03:29:25ned.deilylinkissue38329 messages
2019-10-01 03:29:25ned.deilycreate