Use the SPDX license name in setup.py as required by PEP-639
#365
Conversation
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
jborean93
reviewed
Sep 11, 2025
Reference: https://peps.python.org/pep-0639/ Signed-off-by: Aurélien Bompard <[email protected]>
jborean93
approved these changes
Sep 15, 2025
|
Thanks for fixing this. |
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.
The license tag in
setup.pyis currently just the name of the license file. This confuses license checkers such as https://github.com/dhatim/python-license-check.It also shows up weirdly on PyPI:
There is a standard for this metadata field, it's PEP 639. This commit implements it, there is no other change.