Skip to content Skip to sidebar Skip to footer

Pip Version Mismatch In Venv

I am confused about how virtual Python environments work (Python 3.6, using venv). I set up my venv, and activated it in the command line. I would expect that everything I do from

Solution 1:

pip still points to the global one, even when in an venv. python, however, does not and uses the venv.

This means that when you run pip --version, you get your global pip version. when you run python -m pip install --upgrade pip, you're using the venv version of python, which apparently already has the newest pip. To confirm this, you can run python -m pip --version and you should get the latest version as an output.

Post a Comment for "Pip Version Mismatch In Venv"