I started using poetry for my OSS projects and I'm happy with it, but I'd never use it for closed source projects. Poetry simplifies deps, config, pkg build etc

I started using poetry for my OSS projects and I'm happy with it, but I'd never use it for closed source projects. Poetry simplifies deps, config, pkg build etc as it's stored in a single place, but it's way to opinionated. For managing dependencies only, pip tools is easier to use and customize. There's no breaking changes, it's a finished product. Also, I don't want my CI to fail randomly. https://github.com/python-poetry/poetry/pull/6297 https://github.com/python-poetry/poetry/pull/6297 Look at the number of issues in poetry. Some things are not backwards compat, some are broken. If you want reliable, KISS with pip tools. That's my opinion.