From: Senthil Kumaran <senthil@uthcode.com>
Date: Wed, 18 May 2016 03:50:43 +0000 (-0700)
Subject: issue27045 - Use backslash in windows path to script file.
X-Git-Tag: v3.5.2rc1~142
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c9bfc13aa9965dd717ad1f647cdea62f4b2c8112;p=python

issue27045 - Use backslash in windows path to script file.
---

diff --git a/Doc/using/venv-create.inc b/Doc/using/venv-create.inc
index 3928f33b40..c5294786c2 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