setup.cfg->pyproject.toml, setuptools_scm

[dweindl]

• Move most package configuration to pyproject.toml
• Use setuptools_scm for automated generation of version numbers based on git tags
• Remove unnecessary setup.py

[dilpath]

Thanks, so if I commit to main with message "Release 0.2.3" and upload to PyPI, it will have fiddy==0.2.3?

[dweindl]

Thanks, so if I commit to main with message "Release 0.2.3" and upload to PyPI, it will have fiddy==0.2.3?

Almost. It's independent of any commit message, it's just about git tags. If you create a new release on GitHub via https://github.com/ICB-DCM/fiddy/releases/new, set the tag to v0.2.3 it will be deployed to PyPI as fiddy==0.2.3.

If you create an sdist/wheel for any non-tagged version, it will set the version to something like 0.1.2.dev7+gb1d85d5, where the pre-dev part is based on the last tag in the history. This is only relevant for installations of development versions. Setting the package version is independent of any PyPI deployments - the latter will (currently) only be triggered if a release is published on GitHub, not from pushing a v0.2.3 tag alone.

You can run python -m setuptools_scm in your fiddy repo to see which version string a package would currently get.