New submission from serge-sans-paille:
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`
----------
messages: 254845
nosy: serge-sans-paille
priority: normal
severity: normal
status: open
title: virtualenv's activate does not update LD_LIBRARY_PATH
type: enhancement
versions: Python 2.7
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25657>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
