pyproject: support for PEP 639#4143
Merged
hyperupcall merged 1 commit intoOct 12, 2024
Merged
Conversation
Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>
Contributor
|
Thanks for the PR! This section of the codebase is owned by @madskristensen and |
Member
|
Great, thanks!
That's sensible! |
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
3 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 updates the pyproject.toml with the recently accepted PEP 639. Part of the PEP was already there (string-valued license entries), this adds the other part. Marking the table-valued license as deprecated should wait until there is broad support among build backends, I believe.