Of all the python packaging solutions, my favorite is pip-tools because it works with a standard venv setup. Poetry has some great features, but the additional overhead of requiring devs to install and learn a new tool are just not worth it. Also now you need to install poetry in your Docker images and/or production environments.
For a good discussion about package managers in python:<p><a href="https://chriswarrick.com/blog/2023/01/15/how-to-improve-python-packaging/#the-classic-stack" rel="nofollow noreferrer">https://chriswarrick.com/blog/2023/01/15/how-to-improve-pyth...</a><p>From that page: Poetry isn’t compatible with PEP621(metadata in pyproject.toml), or PEP508 (version markers for dependencies in pyproject.toml)<p>Just some additional context for the discussion. I use poetry, (and pipenv) depending on my use case.
I can never go back to any other system for managing Python dependencies. Poetry was a bit flaky up to around v1.2.x but I'm so glad I stuck with it, since v1.5.x it's been superb.
Since this is a discussion on dependency management in Python - does anyone use rye [0] regularly now? I'm interested in using it but want a little more social validation before I try - some issues with package managers only appear after you've invested considerable time.<p>[0]: <a href="https://rye-up.com/" rel="nofollow noreferrer">https://rye-up.com/</a>
I don't know if I've just had particularly bad luck, but over the years I've run into multiple situations where upgrading my dependency manager has completely broken dependency installation.<p>I started using pipenv many years ago since it was the hot new thing, and then it kept happening over and over with new pipenv releases. And then poetry was the hot new thing, so I switched to poetry. And everything was good with poetry for some years... and then within the past few years, it started happening again. New poetry version, something breaks, Google it, set some config toggle, it works. Then another new version, something breaks again, some other config toggle is needed, etc. The least I'd expect of a dependency manager is very careful attention paid to backwards compatibility.<p>And now, based on this thread, I'm wondering if poetry is falling out of fashion and if these other recommendations, like PDM and rye, are going to be the hot new thing.
I love the idea, but after using it on a day to day basis, I think I’m jaded with the number of ways to do packaging in python.<p>I often find my self removing it from the later stages of the multistage Docker images I create just to decrease the amount of contextual overhead. Maybe I’m crazy but npm feels less intrusive for some reason.