I noticed that setuptools-scm is being used for versioning, and the version.py file is being tacked by git. This is a very bad idea. This is because the software version depends on the git SHA1 hash, and the git SHA1 hash depends on the version. This is type of cicular hashing can't be handled by SHA1. This why all of the versions are for "dirty" releases and never for clean working tree.
I would recommend removing the file from git, and then ignoring it in .gitignore.
I noticed that
setuptools-scmis being used for versioning, and theversion.pyfile is being tacked by git. This is a very bad idea. This is because the software version depends on the git SHA1 hash, and the git SHA1 hash depends on the version. This is type of cicular hashing can't be handled by SHA1. This why all of the versions are for "dirty" releases and never for clean working tree.I would recommend removing the file from git, and then ignoring it in
.gitignore.