Skip to main content

Plugin for Poetry to enable dynamic versioning based on VCS tags

Project description

Dynamic versioning plugin for Poetry

Build status Version License: MIT

This package is a plugin for Poetry to enable dynamic versioning based on tags in your version control system, powered by Dunamai.

Since Poetry does not yet officially support plugins (refer to this issue) as of the time of writing on 2019-10-19, this package takes some novel liberties to make the functionality possible. As soon as official support lands, this plugin will be updated to do things the official way.

Installation

Python 3.5 (or newer) and Poetry 0.12.1 (or newer) are required.

  • Run pip install poetry-dynamic-versioning
  • Add this to your pyproject.toml:
    [tool.poetry-dynamic-versioning]
    enable = true
    

Note that you must install the plugin in your global Python installation, not as a dependency in pyroject.toml, because the virtual environment that Poetry creates cannot see Poetry itself and therefore cannot patch it.

Configuration

In your pyproject.toml file, you may configure the following options:

  • [tool.poetry-dynamic-versioning]: General options.
    • enable: Boolean. Default: false. Since the plugin has to be installed globally, this setting is an opt-in per project. This setting will likely be removed once plugins are officially supported.
    • vcs: String. This is the version control system to check for a version. One of: any (default), git, mercurial, darcs, bazaar, subversion, fossil.
    • metadata: Boolean. Default: unset. If true, include the commit hash in the version, and also include a dirty flag if dirty is true. If unset, metadata will only be included if you are on a commit without a version tag.
    • dirty: Boolean. Default: false. If true, include a dirty flag in the metadata, indicating whether there are any uncommitted changes.
    • pattern: String. This is a regular expression which will be used to find a tag representing a version. There must be a named capture group base with the main part of the version, and optionally you can also have groups named stage and revision for prereleases. The default is ^v(?P<base>\d+\.\d+\.\d+)(-?((?P<stage>[a-zA-Z]+)\.?(?P<revision>\d+)?))?$.
    • format: String. Default: unset. This defines a custom output format for the version. Available substitutions:
      • {base}
      • {stage}
      • {revision}
      • {distance}
      • {commit}
      • {dirty}
    • style: String. Default: unset. One of: pep440, semver, pvp. These are preconfigured output formats. If you set both a style and format, then the format will be validated against the style's rules. If style is unset, the default output format will follow PEP 440, but a custom format will only be validated if style is set explicitly.
    • latest-tag: Boolean. Default: false. If true, then only check the latest tag for a version, rather than looking through all the tags until a suitable one is found to match the pattern.
  • [tool.poetry-dynamic-versioning.subversion]: Options specific to Subversion.
    • tag-dir: String. Default: tags. This is the location of tags relative to the root.

Simple example:

[tool.poetry-dynamic-versioning]
enable = true
vcs = "git"
style = "semver"

Implementation

In order to side-load plugin functionality into Poetry, this package does the following:

  • Upon installation, it delivers a zzz_poetry_dynamic_versioning.pth file to your Python site-packages directory. This forces Python to automatically load the plugin after all other modules have been loaded (or at least those alphabetically prior to zzz).
  • It patches builtins.__import__ so that, whenever the first import from Poetry finishes, poetry.console.main will be patched. The reason we have to wait for a Poetry import is in case you've used the get-poetry.py script, in which case there is a gap between when Python is fully loaded and when ~/.poetry/bin/poetry adds the Poetry lib folder to the PYTHONPATH.
  • The patched version of poetry.console.main will then, when called, additionally patch either poetry.poetry.Poetry.create() or poetry.factory.Factory.create_poetry() (depending on your Poetry version) to replace the version from your pyproject.toml file with the dynamically generated version.

Development

Please refer to CONTRIBUTING.md.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

poetry-dynamic-versioning-0.3.0.tar.gz (6.8 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

poetry_dynamic_versioning-0.3.0-py3-none-any.whl (6.5 kB view details)

Uploaded Python 3

File details

Details for the file poetry-dynamic-versioning-0.3.0.tar.gz.

File metadata

  • Download URL: poetry-dynamic-versioning-0.3.0.tar.gz
  • Upload date:
  • Size: 6.8 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: poetry/0.12.17 CPython/3.7.3 Windows/10

File hashes

Hashes for poetry-dynamic-versioning-0.3.0.tar.gz
Algorithm Hash digest
SHA256 1a6001ba767d5cb88008798cf0fd1e2deab475a76b703f3a367ab977958ccae3
MD5 2d46a38d6d23423457d7bec0dfefb20f
BLAKE2b-256 59687a793518787de62ff57c93600398cc82462521ae51cc6216afb5cb64148b

See more details on using hashes here.

File details

Details for the file poetry_dynamic_versioning-0.3.0-py3-none-any.whl.

File metadata

File hashes

Hashes for poetry_dynamic_versioning-0.3.0-py3-none-any.whl
Algorithm Hash digest
SHA256 fdc942b163ed0aacb4defce5a315bb7f3e6345ff27f07eed509bdfd09137d2cd
MD5 9d6f39d684539ac7930381a2981b9448
BLAKE2b-256 3f254b7411d13c93a6c71fa6f96d08d740be293805bb6c586eec1d2ee637dcbe

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page