Skip to content

Migrate from flit to poetry#651

Merged
robin-nitrokey merged 4 commits intomasterfrom
poetry
Jun 2, 2025
Merged

Migrate from flit to poetry#651
robin-nitrokey merged 4 commits intomasterfrom
poetry

Conversation

@robin-nitrokey
Copy link
Member

This PR migrates from flit to poetry as a build system. This makes it easier to manage and keep track of our dependencies.

Side effects of this change are:

  • Instead of using a VERSION file, we specify the version in pyproject.toml.
  • Many targets from the Makefile that are unused are removed. Most of them can be replaced by one-liners using poetry.
  • Dependencies that are not relevant for end users are now defined in dependency groups instead of optional dependencies.

This patch prepares the migration from flit to poetry by:
- explicitly setting version and description in pyproject.toml instead
  of inferring them dynamically,
- removing the VERSION file as it is no longer needed after the previous
  step, and
- adding `poetry check` to the CI.
poetry makes it easier to manage and keep track of the dependencies.
This patch removes many of the unused targets from the Makefile as the
contained operations are now much easier to achieve by running poetry
directly.
This creates a distinction between optional dependencies that are
relevant for end users and dependency groups that are only relevant for
development or CI.
@robin-nitrokey robin-nitrokey merged commit 7589476 into master Jun 2, 2025
50 checks passed
@robin-nitrokey robin-nitrokey deleted the poetry branch June 2, 2025 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments