I thought it would be better to allow easy_install to put the files
where they belong. I was just hoping that in a .cshrc I could say
something like:
set path=($path `python -c 'import setuptools; print
setuptools.path_to_scripts'`)
or in a .profile:
export PATH="$PATH":`python -c 'import setuptools; print
setuptools.path_to_scripts'`
This way, if I get a new version of python or what have you, my path
is automatically changed to match without me messing with
configurations, etc. I know there must be a way, since obviously
easy_install puts the files there.
I'll dig through the source and see what I can find.
Reid
On Jul 14, 2006, at 2:40, Phillip J. Eby wrote:
At 10:04 PM 7/13/2006 -0700, Jeffrey Harris wrote:
Hi Reid,
Quick question. I noticed that this installs the script in the
directory /opt/local/Library/Frameworks/Python.framework/Versions/
2.4/bin since the Python I use is from DarwinPorts, which lives
under /opt/local.
To make my login scripts easier to manage, is there a way to get
python to print out that pathname instead of hardcoding it?
Something like 'import setuptools; print setuptools.path;' --
except that it works. :-)
Hmm, I'm not following exactly what you want. How would printing
the path make your login script easier?
To tell you the truth, I really don't know much about setuptools,
though, PJE's much more likely to be able to help you.
You probably want to just tell easy_install to put scripts
somewhere that's already on your PATH, using --script-dir. Try
something like this in your ~/.pydistutils.cfg:
[easy_install]
script_dir=~/bin
This should also work to install easy_install itself to ~/bin, or
if not, just run "ez_setup.py -s ~/bin setuptools".
Or, if you prefer not to mess with configuration files, just always
use "easy_install -s ~/bin whatever" when installing packages.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
