I'm phasing out my usage of in all my side projects. Why? - Pipenv can't...
I'm phasing out my usage of #pipenv in all my #python side projects. Why?
- Pipenv can't package.
- Pipenv will soon always lock (which is slow, if I have to, then might as well us poetry)
- Poetry lock speed is bearable if you set minimum versions on *everything*
- Poetry supports pyproject.toml
- Poetry works fine for both libraries & apps (Pipenv aims to solve the problem of apps, not libraries)
- I figure out how to handle poetry private repos. I never figured that out for pipenv
Self-replies
and
- Poetry has features for preventing accidental install of a private package from public pypi just because they have the same name
A few years ago Poetry wasn't even cross platform & depending on the day the performance could be laughable (possibly because at the time I didn't realize the importance of pinning to a minimum to reduce the list of possibilities poetry must consider when looking for a compatible set of libs)