summaryrefslogtreecommitdiffstats
path: root/Doc/using
diff options
context:
space:
mode:
authorBerker Peksag <berker.peksag@gmail.com>2016-06-27 06:51:40 (GMT)
committerBerker Peksag <berker.peksag@gmail.com>2016-06-27 06:51:40 (GMT)
commit9c1e9d453c9d593f25ff34c09410503a61ebe426 (patch)
tree6038c4e7cc59ad22eb33569a5b6cfc4122b55a95 /Doc/using
parentbddc35643799f1a96693d7a26a82449749ea900d (diff)
downloadcpython-9c1e9d453c9d593f25ff34c09410503a61ebe426.zip
cpython-9c1e9d453c9d593f25ff34c09410503a61ebe426.tar.gz
cpython-9c1e9d453c9d593f25ff34c09410503a61ebe426.tar.bz2
Issue #27393: Fix escaping of venv activate commands on Windows
Patch by Manuel Kaufmann.
Diffstat (limited to 'Doc/using')
-rw-r--r--Doc/using/venv-create.inc4
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/using/venv-create.inc b/Doc/using/venv-create.inc
index c529478..c263cf7 100644
--- a/Doc/using/venv-create.inc
+++ b/Doc/using/venv-create.inc
@@ -89,9 +89,9 @@ venv's binary directory. The invocation of the script is platform-specific:
+-------------+-----------------+-----------------------------------------+
| | csh/tcsh | $ source <venv>/bin/activate.csh |
+-------------+-----------------+-----------------------------------------+
-| Windows | cmd.exe | C:\> <venv>\Scripts\activate.bat |
+| Windows | cmd.exe | C:\> <venv>\\Scripts\\activate.bat |
+-------------+-----------------+-----------------------------------------+
-| | PowerShell | PS C:\> <venv>\Scripts\Activate.ps1 |
+| | PowerShell | PS C:\> <venv>\\Scripts\\Activate.ps1 |
+-------------+-----------------+-----------------------------------------+
You don't specifically *need* to activate an environment; activation just