Export to GitHub

pydbgr - issue #7

Custom install does not find PYTHONPATH definition


Posted on Jun 27, 2010 by Swift Ox

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

Comment #1

Posted on Oct 28, 2010 by Swift Hippo

This is a prblem in easy_install not pydbgr.

Comment #2

Posted on Oct 25, 2014 by Swift Hippo

(No comment was entered for this change.)

Status: Invalid

Labels:
Type-Defect Priority-Medium