Update pyproject.toml to be PEP 621 compatible#320
Merged
mmerklinger merged 2 commits intomainfrom Jan 9, 2025
Merged
Conversation
mmerklinger
force-pushed
the
pep621-compatibility
branch
from
1532126 to
2482c81
Compare
mmerklinger
force-pushed
the
pep621-compatibility
branch
from
2482c81 to
c2a867c
Compare
robin-nitrokey
approved these changes
Jan 9, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR makes
pyproject.tomlfile compatible with PEP 621, which is expected by Poetry 2.0. It also makes the CI pipeline consistently install Poetry from PyPI.I kept the dependencies in the
tool.poetry.dependencies, instead of moving them toproject.dependencies. This requiresproject.dynamic.