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
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:
1.2.3.dev45+g23b6cfd
And each tag generates a version such as:
1.2.3
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
[tool.poetry-dynamic-versioning]
enable = true
vcs = "git"
pattern = "^(?P<base>\\d+\\.\\d+\\.\\d+)(-?((?P<stage>[a-zA-Z]+)\\.?(?P<revision>\\d+)?))?"
format-jinja = """
{%- if distance == 0 -%}
{{- base -}}
{%- else -%}
{{- base }}.dev{{ distance }}+g{{commit}}
{%- endif -%}
"""
format-jinja-imports = [
{ module = "datetime", item = "datetime" }
]
- Then just run
poetry build
and check the output:
$ ls dist/
my_package-1.2.3.dev45+g23b6cfd-py3-none-any.whl
-
Thanks to mtkennerly for giving this example. ↩︎
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