From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Fri, 26 Jul 2019 22:03:23 +0000 (-0700) Subject: bpo-32910: Remove implementation detail in venv documentation. (GH-14968) X-Git-Tag: v3.7.5rc1~220 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=4b6421c61e9335253ea7004f2878317b88096c30;p=thirdparty%2FPython%2Fcpython.git bpo-32910: Remove implementation detail in venv documentation. (GH-14968) (cherry picked from commit 91e49575095ca16d1b67dd8822deeb7885e421da) Co-authored-by: Derek Keeler --- diff --git a/Doc/using/venv-create.inc b/Doc/using/venv-create.inc index 1ada83c07a67..4a795704ed9a 100644 --- a/Doc/using/venv-create.inc +++ b/Doc/using/venv-create.inc @@ -115,10 +115,8 @@ installed in a virtual environment should be runnable without activating it, and run with the virtual environment's Python automatically. You can deactivate a virtual environment by typing "deactivate" in your shell. -The exact mechanism is platform-specific: for example, the Bash activation -script defines a "deactivate" function, whereas on Windows there are separate -scripts called ``deactivate.bat`` and ``Deactivate.ps1`` which are installed -when the virtual environment is created. +The exact mechanism is platform-specific and is an internal implementation +detail (typically a script or shell function will be used). .. versionadded:: 3.4 ``fish`` and ``csh`` activation scripts. diff --git a/Misc/NEWS.d/next/Documentation/2019-07-25-10-30-32.bpo-32910.caLLAe.rst b/Misc/NEWS.d/next/Documentation/2019-07-25-10-30-32.bpo-32910.caLLAe.rst new file mode 100644 index 000000000000..60386a196e7c --- /dev/null +++ b/Misc/NEWS.d/next/Documentation/2019-07-25-10-30-32.bpo-32910.caLLAe.rst @@ -0,0 +1 @@ +Remove implementation-specific behaviour of how venv's Deactivate works.