From: Berker Peksag <berker.peksag@gmail.com>
Date: Mon, 27 Jun 2016 06:51:40 +0000 (+0300)
Subject: Issue #27393: Fix escaping of venv activate commands on Windows
X-Git-Tag: v3.6.0a3~64^2
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=9c1e9d453c9d593f25ff34c09410503a61ebe426;p=python

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 c5294786c2..c263cf741b 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