Looks like there's time for one more round of How do you do Python dependency management? before this year is old 😅
For the record, pip freeze > requirements.txt and virtualenvwrapper (yes, still) FTW. 😜
@carlton pyenv-virtualenvwrapper is still the glue that holds everything together for me. (pipx globally too)
Then pip-tools to freeze/update things in nice ways using `pip-compile` and the `--upgrade` option (which I was slower to adopt).
When working with containers or devs using multiple dev platforms, I only lock/upgrade from inside of the container to avoid macOS or Windows-only deps breaking things (sadly, a not uncommon problem.)
@carlton I don't recommend poetry or pipenv anymore because of dependency resolver issues that they both create. They are fine for small libraries and I will leave it at that.
@pganssle @carlton poetry has never worked well for me for this (it's great for working on one-off libraries, though).
pipenv worked well for me outside of containers, but once everything switched to container-based projects, it added nothing but grief and minutes of network overhead. I'm not sure what it gives me when everything runs inside a container.
@pganssle what about Hatch? Should I be looking at that? (Currently in the “we’ll see if there’s yet another one this time next year” pile 🫠)