There seems to be a problem when virtualenv is used in PowerShell.
When I try to activate my environment in PowerShell like…
env/scripts/activate
.. nothing happens. (the shell prompt should have changed as well as the PATH env. variable .)
I guess the problem is that PowerShell spawns a new cmd. process just for running the activate.bat thus rendering the changes activate.bat does to the shell dead after it completes.
Do you have any workarounds for the issue? (I’m sticking with cmd.exe for now)
Advertisement
Answer
My original answer is now outdated. Now, just use activate.ps1 (rather than activate.bat) to activate from a Powershell environment.
Original answer:
Here‘s a post that contains a Powershell script that 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.