Please provide tags for versions in git. This allows several package management systems (such as MacPorts, see https://trac.macports.org/ticket/42596) to track your software much more easily and enables the use of git describe to generate an appropriate version number in getcommit in setup.py.
However, I'd also like to ask you to avoid relying on calls to git to construct a version number for released packages (I guess it's fine for development versions), because package management systems often don't clone the repository from GitHub when building software, but use GitHub's automatically generated tarballs to avoid the git dependency when downloading, making your code fail.
Please provide tags for versions in git. This allows several package management systems (such as MacPorts, see https://trac.macports.org/ticket/42596) to track your software much more easily and enables the use of
git describeto generate an appropriate version number ingetcommitinsetup.py.However, I'd also like to ask you to avoid relying on calls to git to construct a version number for released packages (I guess it's fine for development versions), because package management systems often don't clone the repository from GitHub when building software, but use GitHub's automatically generated tarballs to avoid the git dependency when downloading, making your code fail.