You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's really nasty to call #!/usr/bin/env python from a top-level script. There are many places where the user environment can leak through.
Instead, have stashcp be something along the lines of:
#!/bin/sh
# Take out things the user might have in their environment that would mess up the python instance.
unset PYTHONPATH
unset PATH
unset LD_LIBRARY_PATH
PYTHONPATH=$STASHCP_PREFIX/lib/python...
PATH=...
exec python2.7 $STASHCP_PREFIX/bin/stashcp.py "$@"
You know the drill - have the install script automatically hardcode in the correct paths (such as $STASHCP_PREFIX).
The text was updated successfully, but these errors were encountered:
It's really nasty to call
#!/usr/bin/env python
from a top-level script. There are many places where the user environment can leak through.Instead, have
stashcp
be something along the lines of:You know the drill - have the install script automatically hardcode in the correct paths (such as
$STASHCP_PREFIX
).The text was updated successfully, but these errors were encountered: