chore: migrate pyproject metadata to PEP 621 [project] table#11
Merged
gregsvo merged 1 commit intoJun 29, 2026
Merged
Conversation
Collaborator
|
It impossible to keep track of all the changes being made across libraries- I really appreciate your help, since this library is growing, and is mission-critical for many users. Thank you! |
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
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 addresses the output of the
poetry checkcommand which currently reports multiple deprecation warnings (and fails underpoetry check --strict). Poetry 2.0 deprecated the legacy[tool.poetry]metadata format and adopted the PEP 621[project]table as the standard way to declare package metadata.Poetry plans to drop this old format, so addressing it now prevents the build from breaking once that support is gone. It also moves the package onto PEP 621, the standard metadata format that build tools can read directly.
This is a followup from #9 dev tooling update, which effectively updated
poetry.lockfile from Poetry 1.8.3 to Poetry 2.4.1pyproject.tomlfile now passes underpoetry check --strict