(original) (raw)

changeset: 100439:50f593ed1469 branch: 3.5 parent: 100437:ab3e4be4b539 user: Berker Peksag berker.peksag@gmail.com date: Mon Mar 07 18:50:49 2016 +0200 files: Doc/library/venv.rst description: 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. diff -r ab3e4be4b539 -r 50f593ed1469 Doc/library/venv.rst --- a/Doc/library/venv.rst Sun Mar 06 18:11:38 2016 -0800 +++ b/Doc/library/venv.rst Mon Mar 07 18:50:49 2016 +0200 @@ -43,11 +43,6 @@ 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 /berker.peksag@gmail.com