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)
See Question&Answers more detail:
os 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…