Hacker News Reader

Comment by marban | Hacker News Reader

I've settled with: Pyenv > python venv > Poetry

  CFLAGS="-march=native -mtune=native" CONFIGURE_OPTS="--enable-optimizations --with-lto=full" pyenv install 3.11.1 --verbose

Same. Though I’m debating swapping out poetry with pip tools.

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

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.

Agreed. We tried using poetry in a monorepo that contains dozens of projects and it seemed annoying to get right. Poetry seems to want only one main project folder?

Have you used pip-tools before? I have used PDM instead of Poetry and was very impressed

https://github.com/pdm-project/pdm

I have. At my last gig at Shopify we used it to manage our requirements since poetry didn’t play nice with some internal dev tools.

I’ve tried PDM as well. It’s definitely nice. Part of me just wants to avoid “all encompassing” tools and use a specific tool for a specific job.

For what its worth, I evaluated pdm, poetry, and pyenv before settling on pip-tools for my workflow. pdm is the only one I would consider trying again (once it is more mature).

Reply on news.ycombinator.com