bpo-32910: Remove implementation detail in venv documentation. (GH-14968)

(cherry picked from commit 91e49575095ca16d1b67dd8822deeb7885e421da)

Co-authored-by: Derek Keeler <d3r3kk@users.noreply.github.com>

diff --git a/Doc/using/venv-create.inc b/Doc/using/venv-create.inc
index af30cbb55980714d2cff8aa0871c5f041800d2b2..1b24721bbcbc3af4ff28e89dcc2f3747c57da27d 100644 (file)
--- a/Doc/using/venv-create.inc
+++ b/Doc/using/venv-create.inc
@@ -118,10 +118,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 (file)
index 0000000..60386a1
--- /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.