Package: Use standard setuptools or uv build backend #766

Activity

1. amotl commented on Jan 13, 2026

   

   amotl

   on Jan 13, 2026

   Last edited by amotl

   ContributorAuthor

   More actions

   I like to use versioningit like introduced per GH-757, but the uv build backend does not support it yet (astral-sh/uv#14137), so my vote is to use the standard setuptools build backend. I think this doesn't prevent using the project with uv and hatch utilities, does it?
2. amotl commented on Jan 13, 2026

   

   amotl

   on Jan 13, 2026

   Last edited by amotl

   ContributorAuthor

   More actions

   build backend: setuptools vs. hatchling

   @surister probably wanted to bring in benefits like outlined in Why Hatch?. I am a happy setuptools user, but didn't want to stop any progress here. Hatch seems to be used on other projects, so I don't have any objections against it, but I would also not object against switching back to setuptools. Please advise.
3. mfussenegger commented on Jan 19, 2026

   

   mfussenegger

   on Jan 19, 2026

   Member

   More actions

   No need to change the build backend. The problems were:

   • Chicken and egg problem with the create_tags.sh script: It can't get the version via setuptools anymore if the version to use is based on the git tag. See Cleanup dev setup #767
   • The PR added hatch as build deps in the pyproject.toml, but the release steps and workflows weren't updated accordingly.
4. mfussenegger

   closed this as completedon Jan 19, 2026
5. amotl commented on Jan 19, 2026

   

   amotl

   on Jan 19, 2026

   ContributorAuthor

   More actions

   Thanks!