From: Andre Delfino <adelfino@gmail.com>
Date: Tue, 1 Sep 2020 06:07:29 +0000 (-0300)
Subject: [doc] Document VIRTUAL_ENV environment variable (GH-21970)
X-Git-Tag: v3.10.0a1~206
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=3584d4b64a5373440f78237eac734831cfd83f79;p=thirdparty%2FPython%2Fcpython.git

[doc] Document VIRTUAL_ENV environment variable (GH-21970)
---

diff --git a/Doc/using/venv-create.inc b/Doc/using/venv-create.inc
index c8f6e8f87d56..8f850a74d413 100644
--- a/Doc/using/venv-create.inc
+++ b/Doc/using/venv-create.inc
@@ -126,6 +126,10 @@ directory containing the virtual environment):
 |             | PowerShell      | PS C:\\> <venv>\\Scripts\\Activate.ps1  |
 +-------------+-----------------+-----------------------------------------+
 
+When a virtual environment is active, the :envvar:`VIRTUAL_ENV` environment
+variable is set to the path of the virtual environment. This can be used to
+check if one is running inside a virtual environment.
+
 You don't specifically *need* to activate an environment; activation just
 prepends the virtual environment's binary directory to your path, so that
 "python" invokes the virtual environment's Python interpreter and you can run