Removing setup.cfg and setup.py from the packaging tutorial

Packaging
101

Maybe consider a “Staff Picks” infobox, clearly marked as personal individual opinions. Hypothetical example:

Staff Picks

I personally like using Hatchling in pipx because it works well for simple and complex packages. – John Doe (henryiii?)

I personally like using Flit in pep517 because I only need the absolute minimum. – John Doe (CAM-Gerlach?)

I personally like using setuptools in twine because it supports building native C extensions. – John Doe (bhrutledge?)

I need a build tool that will make me cry. – Kat

I think it would be useful for overwhelmed readers, without giving any official recommendation.

1 Like
102

I just merged https://github.com/pypa/packaging.python.org/pull/1031, which means that Hatchling is now the default build backend, and setup.{py,cfg} are nowhere to be found.

https://packaging.python.org/en/latest/tutorials/packaging-projects/

PRs with further refinements are welcome. Thanks again @henryiii and @ofek for pushing this forward, and everyone who contributed to the conversation.

18 Likes