Possible Duplicate:
Can I change an an existing virtualenv to ignore global site packages? (like --no-site-package on a new one)
I have a virtualenv set up, with plenty of packages installed that I don't want to reinstall. Is there a way to set up this existing virtualenv so that it does not use the global site-packages directory?
FYI, this is primarily motivated by getting this warning:
UserWarning: Module X was already imported from
every time I start up, e.g., mercurial.
Related, but doing the inverse: Revert the `--no-site-packages` option with virtualenv. This implies that all I need is a lib/no-global-site-packages.txt
file, but an empty one of those seems to have no effect.