tl;dr: Why is pip's version reset to 10.0.1 every time I create a new virtual environment and not automatically cloned from my global 18.0 installation?
Every time I create a new virtual environment I'm told that my
pip is outdated. I run
$ pip install --upgrade pip
And get the following output:
Collecting pip Using cached https://files.pythonhosted.org/packages/5f/25/e52d3f31441505a5f3af41213346e5b6c221c9e086a166f3703d2ddaf940/pip-18.0-py2.py3-none-any.whl Installing collected packages: pip Found existing installation: pip 10.0.1 Uninstalling pip-10.0.1: Successfully uninstalled pip-10.0.1 Successfully installed pip-18.0
pip -V outside of a virtual environment returns
pip 18.0 from /usr/lib/python3.7/site-packages/pip (python 3.7)
So the outdated version is only created when I create a new virtual environment.
Is this a feature of python's virtual environment module?
For the record, the command I run to create a new virtual environment is:
$ python -m venv <venv>
I installed it by running
$ pacman -S python python-pip
I am running it in Arch and the output of
python -V is