This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author willingc
Recipients Graham.Oliver, docs@python, r.david.murray, willingc
Date 2015-06-02.02:30:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1433212231.71.0.77577503315.issue24356@psf.upfronthosting.co.za>
In-reply-to
Content
Current version
Each virtual environment has its own Python binary (allowing creation of environments with various Python versions) and can have its own independent set of installed Python packages in its site directories.

Another suggested revision
Since its introduction in Python 3.3, venv may be used to create a virtual environment with its own Python binary and optionally its own independent set of installed Python packages in its site directories. Multiple virtual environments permit various Python versions to exist on a system.

David and Graham,
Perhaps moving the "see also" box (see also Python Packaging User Guide: Creating and using virtual environments) closer to the top, perhaps under the pep reference, would be helpful for the user.

Virtual environments are confusing for those new to Python since there are many "env"s such as venv, pyvenv, virtualenv, virtualenvwrapper, pyenv tool, and myenv used in many examples.

Carol
History
Date User Action Args
2015-06-02 02:30:31willingcsetrecipients: + willingc, r.david.murray, docs@python, Graham.Oliver
2015-06-02 02:30:31willingcsetmessageid: <1433212231.71.0.77577503315.issue24356@psf.upfronthosting.co.za>
2015-06-02 02:30:31willingclinkissue24356 messages
2015-06-02 02:30:31willingccreate