3 ms·

I just discovered this after using (and being annoyed by) pipenv. I’ve heard good things about poetry, but I guess my big mystery is why either of them even exi

• ak217 4y ago
  pip-tools has a minimalistic design philosophy, while poetry and pipenv have a maximalistic one. In other words, pip-tools tries to do one thing well, while poetry and pipenv try to do about a dozen different things well and have various opinions on how to do them. Minimalistic tools often lose out to maximalistic ones in the short term, only to win out in the long term as the maximalistic ones lose the momentum and resources needed to maintain their feature set. pip-tools was never advertised as well as poetry or pipenv, despite in my opinion being a better tool for the job, and having a best-in-class dependency resolver.
  • Tainnor 4y ago
    > Minimalistic tools often lose out to maximalistic ones in the short term, only to win out in the long term as the maximalistic ones lose the momentum and resources needed to maintain their feature set. I don't think this is true. Pipenv and poetry's feature set largely coincides with the feature set of similar tools in other languages (e.g. bundler, cargo). Some such tools have even larger feature sets (e.g. maven, gradle). Nonetheless, these tools haven't lost out to "smaller tools", but have become standard tools in their respective communities. The problem in the Python ecosystem is fragmentation. Nobody can agree on what the right tool for the job is, so everyone uses something different, dependencies/projects don't always work well with all tools, etc.