From 9c1e9d453c9d593f25ff34c09410503a61ebe426 Mon Sep 17 00:00:00 2001 From: Berker Peksag Date: Mon, 27 Jun 2016 09:51:40 +0300 Subject: [PATCH] Issue #27393: Fix escaping of venv activate commands on Windows Patch by Manuel Kaufmann. --- Doc/using/venv-create.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/using/venv-create.inc b/Doc/using/venv-create.inc index c5294786c21..c263cf741b3 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 /bin/activate.csh | +-------------+-----------------+-----------------------------------------+ -| Windows | cmd.exe | C:\> \Scripts\activate.bat | +| Windows | cmd.exe | C:\> \\Scripts\\activate.bat | +-------------+-----------------+-----------------------------------------+ -| | PowerShell | PS C:\> \Scripts\Activate.ps1 | +| | PowerShell | PS C:\> \\Scripts\\Activate.ps1 | +-------------+-----------------+-----------------------------------------+ You don't specifically *need* to activate an environment; activation just