Re:Show HN: Hatch 1.0.0 – Modern, extensible Python project ...
by JackC on Thursday April 28, 2022 @11:36AM
(#31193818)
> Poetry is mainly used for managing an _application_ and its dependencies
I'm surprised to hear that view, since when I looked into poetry it seemed more designed for libraries than for (web) applications. I'm thinking specifically about this thread about whether it would be desirable to have a config file option for the --no-root command line flag: https://github.com/python-poetry/poetry/issues/2458
Re:Show HN: Hatch 1.0.0 – Modern, extensible Python project ...
by henryiii on Thursday April 28, 2022 @12:00PM
(#31194191)
Poetry does several things by default that are bad for libraries - see https://iscinumpy.dev/post/poetry-versions/ for some details.
Re:Show HN: Hatch 1.0.0 – Modern, extensible Python project ...
by techdragon on Friday April 29, 2022 @01:54AM
(#31201877)
Oh yeah, that takes me back, that’s my issue right there. I can’t believe how I had to get so heavy handed in the comments to get people to stop debating the validity of the idea. Hadn’t worked on the project that needed it in a while so I forgot it wasn’t fixed yet, which is a bit disappointing considering.
Re:Show HN: Hatch 1.0.0 – Modern, extensible Python project ...
by kungfufrog on Thursday April 28, 2022 @07:15PM
(#31199414)
Hey, thanks for taking the time to respond. I also wanted to say thanks for hatch, I can see this problem space is something you care a lot about! I will definitely give it a go at the next opportunity and see how I can fit it into my workflow.
I have to say I do like a lot of the design decisions that have gone into hatch. Regardless, it is great to have more compelling options being worked on, and eventually something will get it "right" enough for the important use cases that it becomes a de facto standard and then hopefully a "blessed" option that everyone can rally around.
Poetry is mainly used for managing an _application_ and its dependencies whereas Hatch is more agnostic to the project type and offers plugin-based functionality for the entire workflow (versioning, tox-like environments, publishing) so you can easily build things other than wheel/sdist, test in a Docker container, etc.
Hatch also strictly adheres to standards and eagerly adopts whatever behavior new PEPs dictate while Poetry has a persistent unwillingness to adopt new standards if they are deemed suboptimal (see comments on PEP 621 [1] and PEP 665 [2])
As such, locking support is temporarily blocked https://ofek.dev/hatch/latest/meta/faq/#libraries-vs-applica...
You can continue using other tools like Poetry at the same time https://ofek.dev/hatch/latest/meta/faq/#interoperability
By the way I very much appreciate the eye for design/UX of Poetry's creator, we also share strong opinions on pipenv :)
[1]: https://discuss.python.org/t/5243/12
[2]: https://github.com/python-poetry/poetry/issues/4710#issuecom...