On Sat, Apr 1, 2017 at 12:03 AM, Carl Caulkett <carl.caulk...@gmail.com> wrote: > I've just started to investigate VirtualEnvironments as a means of > preventing my 3rd party code becoming chaotic. I've discovered that > venv's can be managed quite effectively using Powershell. When > Activate.ps1 is run, the PowerShell changes to indicate that the venv > is active which is nice. However despite the official documention, > there doesn't seem to be a corresponding Deactivate.ps1. There is a > deactivate.bat but that doesn't appear to switch the paths back to > their pre-env state.
Please read the contents of Activate.ps1. The way the `deactivate` function works should be obvious. -- https://mail.python.org/mailman/listinfo/python-list
