3 ms·
What I don't really get is this: why can't you just prepend the virtualenv to the PATH and be good with it? That is only required obviously if you're using bas
by heavenlyblue 8y ago
What I don't really get is this: why can't you just prepend the virtualenv to the PATH and be good with it?
That is only required obviously if you're using bash scripts which can't be directed to an actual python binary.
- pseudalopex 8y ago"activate" prevents accidentally nesting environments. It also changes the prompt to show which one is active. Running "deactivate" is easier than changing the environment variables back yourself.
- JNRowe 8y agoUnless you change state yourself in the mean time. `deactivate` changes `$PATH` back to what it was when you ran `activate` for example, which isn’t likely to be what you want if you’ve changed it since. At least with a subshell you can know what state you’re returning to with <C-d>. That is part of the problem with the `virtualenv` story in my eyes. It offers the illusion of isolation, but falls down in quite a few ways which are annoying when they do pop up.