Use setuptools-scm to control version

[PicoCentauri]

Use setuptools-scm to automatically create the version string based on git tag. For example for the current PR this would be

torch-pme-0.1.1.dev3+g2f000d0

using these systems makes comparisons between developer version easier.

Contributor (creator of pull-request) checklist

• Tests updated (for new features and bugfixes)?
• Documentation updated (for new features)?
• Issue referenced (for PRs that solve an issue)?

Reviewer checklist

• CHANGELOG updated with public API or any other important changes?

---

📚 Documentation preview 📚: https://torch-pme--125.org.readthedocs.build/en/125/

[Luthaf]

The setup is producing torch_pme-0.1.dev1+g21ae94a-py3 as a version number on CI, is this expected? Maybe a missing checkout depth on github actions.

[PicoCentauri]

The setup is producing torch_pme-0.1.dev1+g21ae94a-py3 as a version number on CI, is this expected? Maybe a missing checkout depth on github actions.

But isn't the action checking out the current branch?

[Luthaf]

The action is doing a shallow fetch by default, and does not pull tags/history. There is an option to load the history

[Luthaf]

are you sure about this? I would think we need this file included in the sdist so we have the same version when building the wheels from the sdist as when building wheels from the git checkout.

[PicoCentauri]

No I was not. But I tried and the _version.py is in the wheel and for the sdist it will be created again. So seems to be okay to have this here.

[PicoCentauri]

Ahh you might be right with the sdist.

[PicoCentauri]

I added an ignore for check-manifest. This fixes the issue and we have a _version.py in the sdist.

[PicoCentauri]

version seems to be fine now.

torch_pme-0.1.1.dev4%2Bgc83b853-0