This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author godaygo
Recipients godaygo, paul.moore, steve.dower, tim.golden, zach.ware
Date 2018-02-22.11:38:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1519299488.62.0.467229070634.issue32910@psf.upfronthosting.co.za>
In-reply-to
Content
There was a related issue, which was closed https://bugs.python.org/issue26715.

If virtual environment was activated using Powershell script - Activate.ps1, the Deactivate.ps1 was not created, while the documentation says that it should.

"You can deactivate a virtual environment by typing “deactivate” in your shell. The exact mechanism is platform-specific: for example, the Bash activation script defines a “deactivate” function, whereas on Windows there are separate scripts called deactivate.bat and Deactivate.ps1 which are installed when the virtual environment is created."

Way to reproduce under Windows 10, Python 3.6.4

1. Open elevated Powershell (Administrator access).
2. Activate virtual environment using Activate.ps1.
3. There is no Deactivate.ps1

Also, when the environment was activated with Activate.ps1, `deactivate` will not work. On the other hand, if the environment was activated simply with `activate` (it works) in Powershell, `deactivate` will also work.
History
Date User Action Args
2018-02-22 11:38:08godaygosetrecipients: + godaygo, paul.moore, tim.golden, zach.ware, steve.dower
2018-02-22 11:38:08godaygosetmessageid: <1519299488.62.0.467229070634.issue32910@psf.upfronthosting.co.za>
2018-02-22 11:38:08godaygolinkissue32910 messages
2018-02-22 11:38:08godaygocreate