Issue #27393: Fix escaping of venv activate commands on Windows

Patch by Manuel Kaufmann.

diff --git a/Doc/using/venv-create.inc b/Doc/using/venv-create.inc
index c5294786c219249a1eacfa0bd9a178f0b55533ac..c263cf741b3c9675b295f976ce2e9a8bf27f8769 100644 (file)
--- 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