Poetry: Automatically generate package version from git commit
All notes in this series:
- Poetry: Fixing dubious ownership error
- Poetry: build.py example
- Poetry: Automatically generate package version from git commit
- Poetry: Fix warning about sources
- Poetry: Running Black and isort with pre-commit hooks
- Poetry: Fixing permission error when upgrading dulwich
- NiceGUI with Click, Poetry, auto-reload and classes
- Poetry: Offline installation of packages
- Run Poetry command as systemd service
- GitLab CI and poetry-dynamic-versioning
- Poetry: install alpha builds
- Upgrade version of pkginfo used by Poetry
When building a Python package that is stored in git, it can be convenient to automatically generate the package version from the git commit and/or tag. That way there is no need to manually “bump” the version number in your Python code. Instead, each commit in git automatically generates a version such as:
And each tag generates a version such as:
Using setup.py build
, this could be done using setuptools_scm
, but using setup.py
in this manner is deprecated.
Instead, we can perform our build using Poetry, and use the poetry-dynamic-versioning
plugin to replace setuptools_scm
.
Steps §
- Run
poetry self add "poetry-dynamic-versioning[plugin]"
to install thepoetry-dynamic-versioning
plugin. - Add the following to your
pyproject.toml
:1
- Then just run
poetry build
and check the output:
Bonus: Python imports §
If you want to have some fun, you can use Python imports within format-jinja
if you first specify them within format-jinja-imports
.
For example, this:
Is equivalent to:
Then you could, e.g. read the version string from file at /tmp/version_string.txt
if building on Linux:
Using poetry-dynamic-versioning with GitLab §
If using poetry-dynamic-versioning with GitLab, you may find these notes helpful.
Thanks to mtkennerly for giving this example. ↩︎