Closed msabramo closed 11 years ago
Hi Marc,
Thanks for the issue.
Part of the process of building a terrarium involves making the virtual environment "relocatable." As a consequence of this process, all of the scripts in bin
are updated with relative paths. bin/pip
is actually just a python script:
$ ~/foobar
> less bin/pip
#!/usr/bin/env python2.7
...
The env
she-bang causes your shell to use whatever python2.7 is available, in this case, the global one. That is why you are seeing the global packages.
The only ways I know around this issue are:
source testenv/bin/activate; pip freeze
testenv/bin/python testenv/bin/pip freeze
If this doesn't make any sense, let me know.
Ah, that makes sense. I forgot that's how relocatable virtualenvs work. Thanks for the explanation!
It looks like the Terrarium-created virtualenvs include site-packages? Should they not so that they are isolated from the system Python?