diff options
| author | Serhiy Storchaka <storchaka@gmail.com> | 2023-07-22 18:35:22 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-07-22 18:35:22 (GMT) |
| commit | f8b7fe2f2647813ae8249675a80e59c117d30fe1 (patch) | |
| tree | 16fcc31b7ebd0ae7ada477ec1d3594428505e64c /Doc/library/venv.rst | |
| parent | 26e08dfdd7ac1b3d567d30cd35e4898121580390 (diff) | |
| download | cpython-f8b7fe2f2647813ae8249675a80e59c117d30fe1.zip cpython-f8b7fe2f2647813ae8249675a80e59c117d30fe1.tar.gz cpython-f8b7fe2f2647813ae8249675a80e59c117d30fe1.tar.bz2 | |
gh-106948: Add standard external names to nitpick_ignore (GH-106949)
It includes standard C types, macros and variables like "size_t",
"LONG_MAX" and "errno", and standard environment variables like "PATH".
Diffstat (limited to 'Doc/library/venv.rst')
| -rw-r--r-- | Doc/library/venv.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Doc/library/venv.rst b/Doc/library/venv.rst index 9e56725..2482441 100644 --- a/Doc/library/venv.rst +++ b/Doc/library/venv.rst @@ -60,7 +60,7 @@ running from a virtual environment. A virtual environment may be "activated" using a script in its binary directory (``bin`` on POSIX; ``Scripts`` on Windows). -This will prepend that directory to your :envvar:`!PATH`, so that running +This will prepend that directory to your :envvar:`PATH`, so that running :program:`python` will invoke the environment's Python interpreter and you can run installed scripts without having to use their full path. The invocation of the activation script is platform-specific @@ -100,10 +100,10 @@ In order to achieve this, scripts installed into virtual environments have a "shebang" line which points to the environment's Python interpreter, i.e. :samp:`#!/{<path-to-venv>}/bin/python`. This means that the script will run with that interpreter regardless of the -value of :envvar:`!PATH`. On Windows, "shebang" line processing is supported if +value of :envvar:`PATH`. On Windows, "shebang" line processing is supported if you have the :ref:`launcher` installed. Thus, double-clicking an installed script in a Windows Explorer window should run it with the correct interpreter -without the environment needing to be activated or on the :envvar:`!PATH`. +without the environment needing to be activated or on the :envvar:`PATH`. When a virtual environment has been activated, the :envvar:`!VIRTUAL_ENV` environment variable is set to the path of the environment. |