This change addresses issue: https://github.com/regisf/virtualenvwrapper-powershell/issues/25, where you are unable to call workon after calling deactivate. Forcing the reload resolves the issue for me. I tested this on Powershell version 5.1, but checking the Microsoft docs the -force parameter is available back through version 3.
This change addresses issue: https://github.com/regisf/virtualenvwrapper-powershell/issues/25, where you are unable to call workon after calling deactivate. Forcing the reload resolves the issue for me. I tested this on Powershell version 5.1, but checking the Microsoft docs the
-force
parameter is available back through version 3.