I've marked this as a question because I think we need to work out the details, but it turns out that setuptools-scm doesn't work outside of a git repo, which can be annoying for deployment.
We could just move to something else (uv_build, hatchling), but the advantage of setuptools-scm is that it dynamically generates the package version from git tags, which is convenient. We could not use it for programs, just libraries, or something, but it might be cleaner to just make the switch, even if it means users have to manually update the version number. I think this might be easiest. We could add a CI workflow to check that the git tag version and package version match.
Reported by Ryan (@TinyMarsh).
I've marked this as a question because I think we need to work out the details, but it turns out that
setuptools-scmdoesn't work outside of a git repo, which can be annoying for deployment.We could just move to something else (
uv_build,hatchling), but the advantage ofsetuptools-scmis that it dynamically generates the package version from git tags, which is convenient. We could not use it for programs, just libraries, or something, but it might be cleaner to just make the switch, even if it means users have to manually update the version number. I think this might be easiest. We could add a CI workflow to check that the git tag version and package version match.Reported by Ryan (@TinyMarsh).