So, the project you linked has a pyproject.toml file uses flit: requires = ["flit_core >=3.2,<4"] build-backend = "flit_core.buildapi" Python.org defa

So, the project you linked has a pyproject.toml file uses flit: requires = ["flit_core >=3.2,<4"] build-backend = "flit_core.buildapi" Python.org defaults to using hatchling in the docs[1]. PyPA has a sample repository using setuptools[2]. This project is linked from Python.org on this page.[3] Python.org recommends using setuptools under packaging recommendations as well, with no mention of hatchling or flit even on that page.[4] No wonder so many devs are frustrated about this. I've been writing mostly Python for work and fun the past 11 years and I'm f*cking confused what tools to use. When I start a new side project I don't know whether a tool is going to exist and still work in a few years, because there's 10 tools trying to do the same things and it's not clear what the community is actually getting behind. [1]: https://packaging.python.org/en/latest/tutorials/packaging-projects/#creating-pyproject-toml https://packaging.python.org/en/latest/tutorials/packaging-p... [2]: https://github.com/pypa/sampleproject/blob/main/pyproject.toml https://github.com/pypa/sampleproject/blob/main/pyproject.to... [3]: https://packaging.python.org/en/latest/guides/distributing-packages-using-setuptools/ https://packaging.python.org/en/latest/guides/distributing-p... [4]: https://packaging.python.org/en/latest/guides/tool-recommendations/ https://packaging.python.org/en/latest/guides/tool-recommend...