docs: clarify PEP 639 license fields and setuptools minimum - #2143
Open
harshitethic wants to merge 1 commit into
Open
harshitethic wants to merge 1 commit into
harshitethic wants to merge 1 commit into
Conversation
sinoroc
reviewed
Sep 28, 2026
Comment on lines
+326
to
+327
| :pep:`639` defines two fields for modern license metadata. They serve | ||
| different purposes and can be used independently: |
Contributor
There was a problem hiding this comment.
As PEP 639 itself says, the canonical specification is at https://packaging.python.org/en/latest/specifications/core-metadata/#core-metadata, which is what should be linked instead of PEP639 I believe. Maybe it would make sense to change this in the scope of this pull request?
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.
Summary
Clarify two ambiguities in the license / license-files guidance.
Fixes #1854.
📚 Documentation preview 📚: https://python-packaging-user-guide--2143.org.readthedocs.build/en/2143/