kamawanu / googlecode-pydbgr

Automatically exported from code.google.com/p/pydbgr
GNU General Public License v3.0
0 stars 0 forks source link

Custom install does not find PYTHONPATH definition #7

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Perform install into custom directory thus:
sudo easy_install -n --install-dir=/opt/epd/lib/python2.6/site-packages 
pydbgr-0.1.4-py2.6.egg

What is the expected output? What do you see instead?
TEST FAILED: /opt/epd/lib/python2.6/site-packages does NOT support .pth files
error: bad install directory or PYTHONPATH
=========================================================
However, PYTHONPATH is set as follows:
[mannucci@localhost ~/installers]$ echo $PYTHONPATH
/opt/epd/lib/python2.6/site-packages

What version of the product are you using? On what operating system?
pydbgr-0.1.4-py2.6.egg, with Enthought python install in /opt/epd/bin and 
regular python install in /usr/bin for Linux Fedora 7.

Please provide any additional information below.
The program does not seem to receive the value of PYTHONPATH, which is set 
prior to my executing the program. I am using tcsh. 

Additional output is:
=============================================
The
installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

    /opt/epd/lib/python2.6/site-packages

and your PYTHONPATH environment variable currently contains:

    ''

==============================================

However, as I pointed out, the PYTHONPATH variable is set to the correct 
location. It appears as an empty string above. 

Thanks for your help.

-Tony

Original issue reported on code.google.com by aman...@yahoo.com on 27 Jun 2010 at 10:38

GoogleCodeExporter commented 8 years ago
This is a prblem in easy_install not pydbgr.

Original comment by rocky.bernstein on 28 Oct 2010 at 12:05

GoogleCodeExporter commented 8 years ago

Original comment by rocky.bernstein on 25 Oct 2014 at 5:31