PyTaxonKit uses versioneer to read version numbers from the git repo at deploy time. Typically, for Python packages, I configure versioneer to drop a mypackage/_version.py file in the package itself. When I originally configured versioneer for PyTaxonKit, I followed a similar strategy without thinking too much about it.
But PyTaxonKit is not a package, it's a single module. So when it is installed into the environment, the _version.py file is placed alongside it outside of any package. This is what experts in the field call Not Great.
I updated the PyTaxonKit config so that it would create a pytaxonkit_version.py file rather than just _version.py. While I was at it, I also upgraded the vendored versioneer bundled in the repo, which appears to work fine with Python 3.12.
PyTaxonKit uses versioneer to read version numbers from the git repo at deploy time. Typically, for Python packages, I configure versioneer to drop a
mypackage/_version.pyfile in the package itself. When I originally configured versioneer for PyTaxonKit, I followed a similar strategy without thinking too much about it.But PyTaxonKit is not a package, it's a single module. So when it is installed into the environment, the
_version.pyfile is placed alongside it outside of any package. This is what experts in the field call Not Great.I updated the PyTaxonKit config so that it would create a
pytaxonkit_version.pyfile rather than just_version.py. While I was at it, I also upgraded the vendored versioneer bundled in the repo, which appears to work fine with Python 3.12.