Closed fredrikaverpil closed 8 years ago
Actually, this might be a virtualenv issue rather than a PySide issue.
It seems pip list
is returning whatever is installed in the system-wide python/pip when "activated" in a relocated virtualenv. However, if the full path to the virtualenv's pip is specified, pip list
will return the modules only installed into the virtualenv.
I will close the issue in this repository.
First I create a virtualenv and pip install PySide into it.
PySide works fine:
Then I
deactivate
, make the virtualenv relocatable and move the virtualenv. The PySide module is not found:However, if I specify the full path to the virtualenv's
python
executable, the PySide module is found:This is all on Ubuntu 14.04.3 and I do no see this behavior on OS X or Windows.