PEP639 formatting #211
Open
PEP639 formatting #211
+8
−3
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
mpkorstanje
reviewed
Sep 28, 2025
There was a problem hiding this comment.
Passes the smell test, but haven't read PEP639. I'll defer that to @kieran-ryan .
kieran-ryan
requested changes
Sep 28, 2025
setuptools v77.0.0 introduces support for PEP 639 licence declarations
|
@kieran-ryan is this good to merge now? |
@mpkorstanje gonna verify locally tonight… just to ensure is packaging artifacts as before 👍 |
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.
🤔 What's changed?
Updated how license metadata is specified in pyproject.toml file
⚡️ What's your motivation?
Be compliant with PEP639
🏷️ What kind of change is this?
♻️ Anything particular you want feedback on?
📋 Checklist: