diff options
| -rw-r--r-- | Doc/using/venv-create.inc | 6 | ||||
| -rw-r--r-- | Misc/NEWS.d/next/Documentation/2019-07-25-10-30-32.bpo-32910.caLLAe.rst | 1 |
2 files changed, 3 insertions, 4 deletions
diff --git a/Doc/using/venv-create.inc b/Doc/using/venv-create.inc index 46bf0b4..cf5af43 100644 --- a/Doc/using/venv-create.inc +++ b/Doc/using/venv-create.inc @@ -123,10 +123,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 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. |