Very tangential, but wanted to share a small QoL trick that makes using poetry (and venv in general) much nicer...
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:
PATH_add .venv/bin
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