System PIP instead of virtualenv PIP by default?

Question

After using virtualenv with pip off-and-on for a couple of days, I\'ve found that the version of PIP that is used after the virtualenv is actived is the global PIP instead o

Answer 1

It is not the first time I see someone reporting the same issue. I don't know what is happening, but some people discourage the use o source /path/to/venv/bin/activate because it can mess up your $PATH.

There is a way pip will always respect your virtualenv: don't rely on $PATH. Use:

/path/to/venv/bin/pip install MYPACKAGE

It would be nice to find out what is happening to you and share your solution with others. Meanwhile, it may be ok to use the absolute path to pip.