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

(cherry picked from commit 91e4957509)

Co-authored-by: Derek Keeler <d3r3kk@users.noreply.github.com>
This commit is contained in:
Miss Islington (bot) 2019-07-26 15:04:28 -07:00 committed by GitHub
parent 886e66d111
commit 06e8fc95d1
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 4 deletions

View file

@ -118,10 +118,8 @@ installed in a virtual environment should be runnable without activating it,
and run with the virtual environment's Python automatically. and run with the virtual environment's Python automatically.
You can deactivate a virtual environment by typing "deactivate" in your shell. You can deactivate a virtual environment by typing "deactivate" in your shell.
The exact mechanism is platform-specific: for example, the Bash activation The exact mechanism is platform-specific and is an internal implementation
script defines a "deactivate" function, whereas on Windows there are separate detail (typically a script or shell function will be used).
scripts called ``deactivate.bat`` and ``Deactivate.ps1`` which are installed
when the virtual environment is created.
.. versionadded:: 3.4 .. versionadded:: 3.4
``fish`` and ``csh`` activation scripts. ``fish`` and ``csh`` activation scripts.

View file

@ -0,0 +1 @@
Remove implementation-specific behaviour of how venv's Deactivate works.