[SOLVED] Problem trying to install python from sources into a local directory

rnturn · 03-08-2016, 01:00 PM

I need to install a Python module into a project directory and not into a systemwide "site-packages" directory. (Only a select few have root access and we will never get it.)

In some cases I've been able to add a section to "setup.cfg" like

Code:

[easy_install]
install_dir = /home/project/python-modules

and making sure that the PYTHONPATH includes "/home/project/python-modules". Then, running

Code:

python setup.py install

would neatly place the module into the target directory.

Now I've got the sources for a module that does not include a "setup.cfg" file. I've tried creating one that includes the "install_dir" directive I showed above. Unfortunately, the build command returns a message that seems to indicate that the build process is not even looking at my "setup.cfg" and proceeds to try and install the module in the systemwide module location.

Question:

Ideas on how to override this default setting?

TIA...

--
Rick

dugan · 03-08-2016, 01:34 PM

I don't know why you're overcomplicating it like this. If you want to put it in a user directory, then it's just:

Code:

python setup.py install --user

or

Code:

pip install <whatever> --user

To install into an arbitrary prefix (for packaging), it's:

Code:

python setup.py install --root=<wherever

This will give you the rest of the options:

Code:

python setup.py --help install

You will never need anything other than a command-line flag after "install".

rnturn · 03-08-2016, 02:02 PM

Quote:

Originally Posted by dugan

I don't know why you're overcomplicating it like this. If you want to put it in a user directory, then it's just:

Maybe because I've never NOT had access to root when installing packages for users before. :^/

What I've found to be working is:

Code:

export PYTHONPATH=${PYTHONPATH}:/home/myhome/lib/python
mkdir /home/myhome/lib/python
cd <module1-src-root>
install setup.py install --home=/home/myhome
cd <module2-src-root>
install setup.py install --home=/home/myhome

Then a simple Python script

Code:

#!/usr/bin/python
import module1
import module2
exit

executes without any errors. Now I'm writing a script to exercise some of the functions available in these packages to make sure things are really working. My testing may point out some subtle differences between the "--user", "--home", etc. switches.

I've had to install these under my home directory as the sysadmins have yet to grant my account the group membership needed to do the installations into the project directory. (Asking to have my account "B" look just like existing account "A" was somehow misinterpreted as "give account B a small subset of account A's capabilities". Gotta love it.) I'm hoping I don't have to reinvent these steps once I get that group membership. My current plan it to merely change "myhome" to the project library subdirectory.

Thanks...

--
Rick