4 commits

Author	SHA1	Message	Date
Miss Islington (bot)	0c64b57e01	[3.8] bpo-37354: Make Powershell Activate.ps1 script static to allow for signing (GH-14967) ... - Remove use of replacement text in the script - Make use of the pyvenv.cfg file for prompt value. - Add parameters to allow more flexibility - Make use of the current path, and assumptions about where env puts things, to compensate - Make the script a bit more 'idiomatic' Powershell - Add script documentation (Get-Help .\.venv\Scripts\Activate.ps1 shows PS help page now (cherry picked from commit 732775d6be) Co-authored-by: Derek Keeler <d3r3kk@users.noreply.github.com>	2019-08-12 14:09:26 -07:00
Brett Cannon	d64ee1a5ba	bpo-32718: Make Activate.ps1 for venv cross-platform and available on all platforms (GH-9321) ... PowerShell Core 6.1 is the cross-platform port of Windows PowerShell. This change updates Activate.ps1 to not make Windows assumptions as well as installing it into the bin/Scripts directory on all operating systems. Requires PowerShell Core 6.1 for proper readline support once the shell has been activated for the virtual environment.	2018-09-21 15:27:26 -07:00
Sorin Sbarnea	90f1d98959	bpo-25351: avoid activate failure on strict shells (GH-3804)	2017-09-29 12:48:11 +01:00
Vinay Sajip	98a74413b9	Issue #22343: Made bash activate script available on Windows.	2017-01-12 17:12:10 +00:00