cpython: ac95719f1803 (original) (raw)

Mercurial > cpython

changeset 100440:ac95719f1803

Issue #21034: Remove outdated paragraph from venv documentation Since Python 3.4, there is no need to install pip and setuptools into a venv manually. [#21034]

Berker Peksag berker.peksag@gmail.com
date	Mon, 07 Mar 2016 18:51:06 +0200
parents	e0df94327586(current diff)50f593ed1469(diff)
children	ee1d44f7d3e7
files
diffstat	1 files changed, 0 insertions(+), 5 deletions(-)[+] [-] Doc/library/venv.rst 5

line wrap: on

line diff

--- a/Doc/library/venv.rst +++ b/Doc/library/venv.rst @@ -43,11 +43,6 @@ Creating virtual environments Common installation tools such as Setuptools and pip work as expected with venvs - i.e. when a venv is active, they install Python packages into the venv without needing to be told to do so explicitly.

Of course, you need to install them into the venv first: this could be
done by running ez_setup.py with the venv activated,
followed by running easy_install pip. Alternatively, you could download
the source tarballs and run python setup.py install after unpacking,
with the venv activated. When a venv is active (i.e. the venv's Python interpreter is running), the attributes :attr:sys.prefix and :attr:sys.exec_prefix point to the base