From c9bfc13aa9965dd717ad1f647cdea62f4b2c8112 Mon Sep 17 00:00:00 2001 From: Senthil Kumaran Date: Tue, 17 May 2016 20:50:43 -0700 Subject: [PATCH] issue27045 - Use backslash in windows path to script file. --- 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 3928f33b40d..c5294786c21 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