3 ms·
The README.rst documents the `egg` subcommand like this: > Creates a new Python project. Think of an "egg" as a new idea. How does this differ from the egg di
by Flimm 9y ago
The README.rst documents the `egg` subcommand like this:
> 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 https://packaging.python.org/glossary/#term-egg
- dharness 9y agoI agree. It is definitely a completely different thing and even though 'egg' is a cool word I wish it was just 'hatch create my-app'
- PrimHelios 9y agoFrom 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.
- pmoriarty 9y agoI 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. [1] - https://www.youtube.com/watch?v=qOH-h-EKKac https://www.youtube.com/watch?v=qOH-h-EKKac
- ofek 9y ago0.4.0 changed the name from `egg` to `new` https://github.com/ofek/hatch/commit/5649b3f6c452b670d919fae1a9d4eebb1fbea5a4 https://github.com/ofek/hatch/commit/5649b3f6c452b670d919fae...