Skip to content

Commit 91e4957

Browse files
d3r3kkzooba
authored andcommitted
bpo-32910: Remove implementation detail in venv documentation. (GH-14968)
1 parent 9d9893a commit 91e4957

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
@@ -123,10 +123,8 @@ installed in a virtual environment should be runnable without activating it,
123123
and run with the virtual environment's Python automatically.
124124
125125
You can deactivate a virtual environment by typing "deactivate" in your shell.
126-
The exact mechanism is platform-specific: for example, the Bash activation
127-
script defines a "deactivate" function, whereas on Windows there are separate
128-
scripts called ``deactivate.bat`` and ``Deactivate.ps1`` which are installed
129-
when the virtual environment is created.
126+
The exact mechanism is platform-specific and is an internal implementation
127+
detail (typically a script or shell function will be used).
130128
131129
.. versionadded:: 3.4
132130
``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)