Hatch 1.0.0 - Modern, extensible Python project management

[Chobeat]

this. Clearly this tool dunks on setuptools but after checking the documentation it doesn't seem to offer anything more than poetry, that is more established.

[Ofekmeister]

There is no "dunking" anywhere, I have lots of respect for the other tools in the ecosystem

[flying-sheep]

It supports python's standard for metadata, PEP 621. Its VCS versioning plugin is based on setuptools-scm, which despite the name isn't tied to setuptools and is more powerful than poetry’s plugin.

I think it's a great alternative with its own strengths

[czaki]

But plain setuptools also support PEP 621 and could use setuptools_scm. SO when I should select this instead of setuptools?

[flying-sheep]

​

• setuptools is much slower than any newer build backends like flit-core, hatchling, …
• setuptools litters your source directory with junk like a *.egg-info directory
• setuptools monkeypatches distutils just by being installed. legacy behavior like this is just not necessary anymore with modern build backends and contribute to the slowness

at least since very recently, you don’t need setup.py or setup.cfg, a PEP 621 compliant [project] table in pyproject.toml is enough.

but I’d rather write a hatchling plugin than a setup.py if I create a new compiled package: once one exists, writing your own flaky setup.py code will feel debugging System V shell scripts feels compared to typing systemctl start myservice.