Message254845
My use cas of virtual env was the following:
1. create a virtual env
2. install a third party shared library and its python wrapper
3. import the wrapper that itself loads the shared library
The problem is that the shared library gets install into <my_env>/lib (which is a normal behavior) but virtualenv's activate does not update LD_LIBRARY_PATH
A possible fix would be to add the following lines into virtualenv's activate:
```
if [ -n "$_OLD_VIRTUAL_LD_LIBRARY_PATH" ] ; then
PATH="$_OLD_VIRTUAL_LD_LIBRARY_PATH"
export LD_LIBRARY_PATH
unset _OLD_VIRTUAL_LD_LIBRARY_PATH
fi
```
and a bit later
```
_OLD_VIRTUAL_LD_LIBRARY_PATH="$LD_LIBRARY_PATH"
LD_LIBRARY_PATH="$VIRTUAL_ENV/lib:$LD_LIBRARY_PATH"
export LD_LIBRARY_PATH
```
in a simialr manner to what is done with `PATH` |
|
Date |
User |
Action |
Args |
2015-11-18 14:48:48 | serge-sans-paille | set | recipients:
+ serge-sans-paille |
2015-11-18 14:48:48 | serge-sans-paille | set | messageid: <1447858128.82.0.165586856524.issue25657@psf.upfronthosting.co.za> |
2015-11-18 14:48:48 | serge-sans-paille | link | issue25657 messages |
2015-11-18 14:48:48 | serge-sans-paille | create | |
|