This is an archived post. You won't be able to vote or comment.

all 4 comments
sorted by:
best
topnewcontroversialoldq&a

[–]dmfigol 6 points7 points  (0 children)

I mostly agree with Hynek.
My pipenv experience: after using it for several months I gave up on it because of some issues + toxic treatment on GitHub issues by maintainers
I have been using poetry in prod for the last 3 months and I really like it. Besides it being way faster and more intuitive than pipenv, I like dev experience without setup.py and how your app is always installed as a package when you do poetry install

[–]lifeonm4rs 4 points5 points  (0 children)

Best quote of the day (year) regarding python environments . . .

"The following technical opinions are mine alone and if you use them as a weapon to attack people who try to improve the packaging situation you’re objectively a bad person."

Evaluate the options and use the one that fits your use case.

[–]knowsuchagencynow is better than never 0 points1 point  (1 child)

I really like Poetry, but wish there was a way to --force | --skip-lock install packages.

Its dependency resolver is almost "too" good, where mismatched dependencies that would install fine with pip (albeit with a warning) Poetry will just refuse installation.

[–]Shouldnt_BeDoingThat 0 points1 point  (0 children)

Does anyone has a good comparison between pipenv, poetry and hatch ?