Re:Show HN: Hatch – A modern project, package, and virtual e...
by PrimHelios on Tuesday September 05, 2017 @10:23AM
(#15175455)
From what I can tell, the egg subcommand doesn't create any kind of egg file, just creates a new project.
But I agree. Creating a new distinct keyword for that command (why not just `hatch new my-app`?) would be far better. I've tried to get into Python packaging, and it's the biggest PITA I've dealt with as a dev.
Re:Show HN: Hatch – A modern project, package, and virtual e...
by pmoriarty on Tuesday September 05, 2017 @02:29PM
(#15177877)
I can recommend this great video from PyCon 2017 which demystifies a lot of Python's packaging process: [1]
But it's still a mess only Rube Goldberg could love.
Re:Show HN: Hatch – A modern project, package, and virtual e...
by ofek on Tuesday September 05, 2017 @12:26PM
(#15176684)
0.4.0 changed the name from `egg` to `new` https://github.com/ofek/hatch/commit/5649b3f6c452b670d919fae...
Re:Show HN: Hatch – A modern project, package, and virtual e...
by Flimm on Tuesday September 05, 2017 @12:52PM
(#15176939)
Thanks ofek, seemingly small things like this make a huge difference.
> Creates a new Python project. Think of an "egg" as a new idea.
How does this differ from the egg distribution format [1] introduced by setuptools, which wheel aims to replace? If it's completely different, couldn't a distinct term be used? Python packaging is confusing enough as it is!
[1] - https://packaging.python.org/glossary/#term-egg