Hi fellow pythonistas, there seems to be a problem when virtualenv is used in PowerShell.
When I try to activate my environment in PowerShell like..
> env
Update: The answer below is out of date. Now, just use activate.ps1
(rather than activate.bat
) to activate from a Powershell environment.
Here's a post which contains a Powershell script which allows you to run batch files that persistently modify their environment variables. The script propagates any environment variable changes back to the calling PowerShell environment.