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 ned.deily, reowen, ronaldoussoren
Date 2011-01-21.07:53:13
SpamBayes Score 1.1412266e-09
Marked as misclassified No
Message-id <1295596396.74.0.795221593719.issue10964@psf.upfronthosting.co.za>
In-reply-to
Content
Adding the symlinks to /usr/local is an option in the OS X installer.  Although it is enabled by default, you can easily disable it in Installer.app by selecting "Customize" and then unchecking the install of the "UNIX command-line tools" package.

The main reason for installing the symlinks by default is, I believe, a historical one.  Using /usr/local/bin/ to refer to an alternate Python is an established custom.  On the other hand, as you point out, adding the OS X framework bin directory to the path is accomplishes the same thing and is more robust and, in fact, necessary if packages are installed that add console scripts (unless a symlink is manually created in /usr/local/bin for the console script).

With the likely ongoing requirement for multiple Python versions for many users, it would be good to have a better way to manage versions than the current rather simplistic approach, i.e. the installer supplied 'Update Shell Profile.command'.
History
Date User Action Args
2011-01-21 07:53:16ned.deilysetrecipients: + ned.deily, reowen, ronaldoussoren
2011-01-21 07:53:16ned.deilysetmessageid: <1295596396.74.0.795221593719.issue10964@psf.upfronthosting.co.za>
2011-01-21 07:53:14ned.deilylinkissue10964 messages
2011-01-21 07:53:13ned.deilycreate