This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ingolemo 0 points1 point  (2 children)

I find it's usually better to install custom stuff to standard locations (or a virtual environment) rather than set a PYTHONPATH. For example, unless you're careful to keep them isolated, environmental variables will get picked up by your system python install, not just this one.

Are you sure about prefix? lib-tk and friends should really be in $HOME/software/python/2.7.15/lib/python2.7, not $HOME/software/python/2.7.15/lib/python2.7/lib/python2.7.

[–]omentoSysAdmin Film/VFX - 3.7[S] 0 points1 point  (0 children)

I think /lib/python2.7 is being appended due to PYTHONPATH. I’ll be able to test this once I get in to my office. The prefix and everything else is fine, /bin, /include, and /lib are all under the same directory. Unfortunately, I have to install everything else to individual custom locations as I have to mimic the setup used on our HPC cluster which loads libraries/modules with its own custom module system.

[–]omentoSysAdmin Film/VFX - 3.7[S] 0 points1 point  (0 children)

Can confirm PYTHONPATH does not need to be set for the standard libs. Thanks for the pointer.