traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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

This commit is contained in:
Derek Keeler 2019-07-26 14:57:11 -07:00 committed by Steve Dower
parent 9d9893a1c8
commit 91e4957509
2 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Doc/using/venv-create.inc
View File

@ -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.

1
Misc/NEWS.d/next/Documentation/2019-07-25-10-30-32.bpo-32910.caLLAe.rst Normal file
View File

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