Issue 778799: scripts destination directory not on default path (original) (raw)

Issue778799

Created on 2003-07-28 08:36 by zenzen, last changed 2022-04-10 16:10 by admin. This issue is now closed.

Messages (2)
msg60360 - (view)	Author: Stuart Bishop (zenzen)	Date: 2003-07-28 08:36
A distutils script that uses the 'scripts' directive will install the scripts in /Library/Frameworks/Versions/2.3/bin This directory is not on the path, and no documentation explains how to *put* it on the path. The end result is that 3rd party python libraries that install command line utilities don't work out of the box. If we need to have scripts and stuff dual homed in /Library/Frameworks/Versions/2.3/bin and /usr/local/bin, distutils will need to be patched to maintain the symlinks (although I personally feel putting anything in /usr/local/bin is a bad idea...). This of course will not be possible for the 2.3.0 release.
msg60361 - (view)	Author: Ronald Oussoren (ronaldoussoren) *	Date: 2006-06-25 21:36
Logged In: YES user_id=580910 Current wisdom is that its better to add the directories inside the framework to your PATH. The binary installers for 2.4.3 and 2.5b1 do this for you (even if the solution used isn't ideal).