Re:Boring Python: dependency management (2022)
by PufPufPuf on Monday February 05, 2024 @04:06AM
(#39258923)
It's better to activate the virtualenv properly:
. .venv/bin/activate
Setting up just the PATH may confuse some tools.
Re:Boring Python: dependency management (2022)
by regularfry on Monday February 05, 2024 @07:11AM
(#39260372)
I personally intensely dislike tools that change the environment based on the directory contents. I use an `exec` script in the root (or parent, sometimes) that just does this:
```
#!/bin/bash
source .venv/bin/activate
exec $SHELL $@
```
That gives me a subshell with the virtual env active, and the path to the virtual env goes into $PS1 so I've got a very visible "you are working in this project" signifier.I don't know why subshells aren't more popular for this sort of thing, they remove a lot of ambiguity (and subsequent opportunities to screw things up) for me.
Instead of having to type "poetry shell" to activate the virtualenv, I use a tool called direnv that automatically modifies envars when you enter a directory - undoing the changes when you leave.
In my direnv config (.envrc) for the directory I write:
To add all the virtualenv executables to PATH. Now I can just call "python/pip" directly and never have to worry if I'm inside my virtualenv or not.N.B. for this you need to update poetry config to ensure virtualenvs are placed in the project directory vs. the default centralised location