7 ms·
But you can have multiple virtual environments in the same directory, which one would it activate? You could also be using an environment that's in a different
by avnigo 4y ago
But you can have multiple virtual environments in the same directory, which one would it activate? You could also be using an environment that's in a different directory, or have one already loaded.
I like the concept potentially meaning less friction, but the implementation may make things more confusing for beginners when you're not explicitly activating an environment in your shell. I think maybe a flag to enable the behavior at runtime would be better than it'd be opt out.
- jdxcode 4y ago.venv, obviously. Just like node and node_modules. No need to make this configurable beyond VIRTUAL_ENV
- coldtea 4y ago>But you can have multiple virtual environments in the same directory, which one would it activate? So don't have many in the same directory. Since the name shall be fixed, you wouldn't be able to anyway (e.g. .venv, similar to .node_modules). Simple as that.