1. Tarek Ziadé
  2. distribute
Issue #35 invalid

Installing 'distribute' with --prefix fails

Laurent Gautier
created an issue

Trying to install 'distribute' with python2.6 and code from the trunk as

python setup.py install --prefix=/some/where

fails with

error: bad install directory or PYTHONPATH

There appear to be one way to reach a later stage in the installation process by doing:

export PYTHONPATH=/some/where python setup.py install --prefix=/some/where

... but it just fails later:

with File "/hohoho/distribute/Distribute/pkg_resources.py", line 526, in resolve raise DistributionNotFound(req) # XXX put more info here pkg_resources.DistributionNotFound: setuptools

Comments (7)

  1. Tarek Ziadé repo owner

    I cannot reproduce the problem when providing a *valid* prefix.

    Can you give us:

    • the full output
    • the nature of /some/where directory (does it contains .pth files ? is it in PYTHONPATH ?)

    Thanks

  2. Laurent Gautier reporter

    Answer to the second question first:

    - the directory is originally *not* in PYTHONPATH, since adding it changes the error message (see my bug report)

    - the directory only contains bin/ and lib/ (containing itself python2.6/lib/site-packages)

    Regarding the first question, I do not have the full ouput anymore and I reinstalled setuptools (I have to get moving on a project - I may be able to give the output a little later).

    In case one does not see how this prevents me from providing the full output, this is because the setup.py for distribute tries nuking any existing setuptools (which is itself something a little disturbing).

    Before install bootstrap.
    Scanning installed packages
    Setuptools installation detected at /usr/lib/python2.6/dist-packages
    Non-egg installation
    Removing elements out of the way...
    Renaming /usr/lib/python2.6/dist-packages/setuptools.egg-info into /usr/lib/python2.6/dist-packages/setuptools.egg-info.OLD.1250361220.46
    
  3. Tarek Ziadé repo owner

    Does it mean the installation worked fine with setuptools ?

    In case one does not see how this prevents me from providing the full output, this is because the setup.py for distribute tries nuking any existing setuptools (which is itself something a little disturbing).

    How this is related ? you should get a full output nevertheless.

    which is itself something a little disturbing

    Yes, but required for 0.6 unfortunately (see the README FAQ)

  4. Laurent Gautier reporter

    Does it mean the installation worked fine with setuptools ?

    Yep.

    How this is related ? you should get a full output nevertheless.

    As mentioned in my earlier post, I do not have the output anymore, and I am currently with too little time to go through the cycle "try to install distribute -> have my setuptools stabbed -> copy the output when it fails -> clean whatever needs to be cleaned -> reinstall setuptools to keep working".

    Yes, but required for 0.6 unfortunately (see the README FAQ)

    I am considering only experimenting further with "distribute" when it stops meddling with other installed packages.

  5. Tarek Ziadé repo owner

    As mentioned in my earlier post, I do not have the output anymore, and I am currently with too little time to go through the cycle [...]

    A ok I thaught you said that setup.py was preventing you from getting the output.

    I am considering only experimenting further with "distribute" when it stops meddling with other installed packages.

    Ok then, unless you want to get the bug fixes we have addressed, you should stick with setuptools and not install the 0.6.x series of Distribute.

    Notice that setuptools is already "meddling" distutils on your system everytime you use easy_install ;)

    Anyways, I am closing this issue due to a lack of information and the fact that I cannot reproduce your problem.

  6. Log in to comment