Should Python 2.6 on OS X deal with multiple easy-install.pth files in $PYTHONPATH?
Posted
by ahd
on Stack Overflow
See other posts from Stack Overflow
or by ahd
Published on 2010-05-08T12:50:19Z
Indexed on
2010/05/08
12:58 UTC
Read the original article
Hit count: 334
I am running ipython from sage and also am using some packages that aren't in sage (lxml, argparse) which are installed in my home directory. I have therefore ended up with a $PYTHONPATH of
$HOME/sage/local/lib/python:$HOME/lib/python
Python is reading and processing the first easy-install.pth it finds ($HOME/sage/local/lib/python/site-packages/easy-install.pth) but not the second, so eggs installed in $HOME/lib/python aren't added to the path. On reading the off-the-shelf site.py, I cannot for the life of me see why it's doing this.
Can someone enlighten me? Or advise how to nudge Python into reading both easy-install.pth files?
Consolidating both into one .pth file is a viable workaround for now, so this question is mostly for curiosity value.
© Stack Overflow or respective owner