Skip to content

Commit 4b6421c

Browse files
bpo-32910: Remove implementation detail in venv documentation. (GH-14968)
(cherry picked from commit 91e4957) Co-authored-by: Derek Keeler <[email protected]>
1 parent ea0f7aa commit 4b6421c

File tree

2 files changed

+3
-4
lines changed

2 files changed

+3
-4
lines changed

Doc/using/venv-create.inc

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -115,10 +115,8 @@ installed in a virtual environment should be runnable without activating it,
115115
and run with the virtual environment's Python automatically.
116116
117117
You can deactivate a virtual environment by typing "deactivate" in your shell.
118-
The exact mechanism is platform-specific: for example, the Bash activation
119-
script defines a "deactivate" function, whereas on Windows there are separate
120-
scripts called ``deactivate.bat`` and ``Deactivate.ps1`` which are installed
121-
when the virtual environment is created.
118+
The exact mechanism is platform-specific and is an internal implementation
119+
detail (typically a script or shell function will be used).
122120
123121
.. versionadded:: 3.4
124122
``fish`` and ``csh`` activation scripts.
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
Remove implementation-specific behaviour of how venv's Deactivate works.

0 commit comments

Comments
 (0)