Problem when LD_LIBRARY_PATH is required to run python

[ajanin]

I'm in a managed environment using my own version of python. As a result, I need to set LD_LIBRARY_PATH to get python to work. In clonevirtualenv.py, around line 63, a python subprocess is opened, but the environment it uses is set to {}. To get it to work in my environment, I changed that to:

     env={'LD_LIBRARY_PATH': os.environ.get('LD_LIBRARY_PATH')},            

I'm adding this issue mostly just to document it in case others search for it rather than suggesting it as a general solution.

[gregswift]

Would definitely like to see this added. It jacks with us because we use SCLs (software collections)

[nickaj]

I'd like to see this added too. I'm working with large clusters and supercomputers where Python is usually provided as a module and requires pulling in LD_LIBRARY_PATH.

[henryzhongsc]

I needed to clone a venv on a cluster as well, and this saved the day. A big thank you from 9 years later :)