From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Mon, 1 Mar 2021 15:07:31 +0000 (-0800)
Subject: [3.8] [doc] Document VIRTUAL_ENV environment variable (GH-21970) (GH-24363)
X-Git-Tag: v3.8.9~49
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=6900a515c8410795f9a8ef2ad38740847a919b6d;p=thirdparty%2FPython%2Fcpython.git

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

(cherry picked from commit 3584d4b64a5373440f78237eac734831cfd83f79)
---

diff --git a/Doc/using/venv-create.inc b/Doc/using/venv-create.inc
index c81aaf15d885..b4089e61fa7b 100644
--- a/Doc/using/venv-create.inc
+++ b/Doc/using/venv-create.inc
@@ -121,6 +121,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