Managing version updates with poetry

[agstephens]

Consider a new approach for version updates and tagging (using CI):

As an illustration, in a poetry-managed package, I would set the git tag first,

git tag x.y.z
git push --tags

then put that version in the pyproject.toml file like

poetry version $(git describe --tags --abbrev=0)

and finally

poetry build

to build the package. Put the poetry part in a github action and you have an automated workflow.

To correctly show the version number within the package, you put

from importlib import metadata
__version__ = metadata.version("package-name")

in the main __init__.py file.

[FObersteiner]

forgot to add two things,

• github action would modify the remote of the repo, one would have to pull after the action completes. This might not be desirable under all circumstances.
• importlib.metadata is a Py 3.8 feature. A < Py 3.8 alternative might be pkg_resources; pkg_resources.get_distribution("nappy").version