[ python-Bugs-778799 ] scripts destination directory not on default path

[SourceForge.net]

Bugs item #778799, was opened at 2003-07-28 10:36
Message generated for change (Comment added) made by ronaldoussoren
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=778799&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Macintosh
Group: Platform-specific
Status: Open
Resolution: None
Priority: 5
Submitted By: Stuart Bishop (zenzen)
Assigned to: Jack Jansen (jackjansen)
Summary: scripts destination directory not on default path

Initial Comment:
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.



----------------------------------------------------------------------

>Comment By: Ronald Oussoren (ronaldoussoren)
Date: 2006-06-25 23:36

Message:
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).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=778799&group_id=5470