cpython: 408b6b3dcf9a (original) (raw)

Mercurial > cpython

changeset 85562:408b6b3dcf9a

Closes #18939: Merged documentation update from 3.3. [#18939]

Vinay Sajip <vinay_sajip@yahoo.co.uk>
date	Fri, 06 Sep 2013 09:51:27 +0100
parents	985384cd6365(current diff)ad09332f856f(diff)
children	8002aee72837
files	Doc/library/venv.rst
diffstat	1 files changed, 14 insertions(+), 0 deletions(-)[+] [-] Doc/library/venv.rst 14

line wrap: on

line diff

--- a/Doc/library/venv.rst +++ b/Doc/library/venv.rst @@ -21,6 +21,7 @@ site directories. Each virtual environm creation of environments with various Python versions) and can have its own independent set of installed Python packages in its site directories. +See :pep:405 for more information about Python virtual environments. Creating virtual environments ----------------------------- @@ -61,6 +62,19 @@ Creating virtual environments ignored from all distutils configuration files to prevent projects being inadvertently installed outside of the virtual environment.

When working in a command shell, users can make a venv active by running an
activate script in the venv's executables directory (the precise filename
is shell-dependent), which prepends the venv's directory for executables to
the PATH environment variable for the running shell. There should be no
need in other circumstances to activate a venv -- scripts installed into
venvs have a shebang line which points to the venv's Python interpreter. This
means that the script will run with that interpreter regardless of the value
of PATH. On Windows, shebang line processing is supported if you have the
Python Launcher for Windows installed (this was added to Python in 3.3 - see
:pep:397 for more details). Thus, double-clicking an installed script in
a Windows Explorer window should run the script with the correct interpreter
without there needing to be any reference to its venv in PATH. +

API ---