3 ms·

pip used to support virtualenvs. pip 0.2 (2008) https://pypi.org/project/pip/0.2/ https://pypi.org/project/pip/0.2/ : > pip is complementary with virtualenv,

pip used to support virtualenvs. pip 0.2 (2008) https://pypi.org/project/pip/0.2/ https://pypi.org/project/pip/0.2/ : > pip is complementary with virtualenv, and it is encouraged that you use virtualenv to isolate your installation. https://pypi.org/project/pip/0.2/#using-pip-with-virtualenv https://pypi.org/project/pip/0.2/#using-pip-with-virtualenv : pip install -E venvpath/ pkg1 pkg2 When was the -E <virtualenv> flag removed from pip and why? pip install --help | grep "\-E"

westurner 2y ago
"PEP 453 – Explicit bootstrapping of pip in Python installations" https://peps.python.org/pep-0453/#changes-to-virtual-environments https://peps.python.org/pep-0453/#changes-to-virtual-environ... : > Python 3.3 included a standard library approach to virtual Python environments through the venv module. Since its release it has become clear that very few users have been willing to use this feature directly, in part due to the lack of an installer present by default inside of the virtual environment. They have instead opted to continue using the virtualenv package which does include pip installed by default. "why venv install old pip?" re: `python -m ensurepip && python -m pip install -U pip` https://github.com/python/cpython/issues/74813 https://github.com/python/cpython/issues/74813
westurner 2y ago
> When was the -E <virtualenv> flag removed from pip and why? Though `pip install --python=... pkg` won't work ( https://github.com/pypa/pip/pull/12068 https://github.com/pypa/pip/pull/12068 ), Now, there's pip --python=$VIRTUAL_ENV/bin/python install pkg