feat: support PEP 639#210
Merged
Merged
Conversation
Collaborator
Author
|
@abravalheri assuming we can't depend on packaging? (Especially a version that's not out yet). Maybe the validation of SPDX classifiers should be optional, just like trove classifiers, based on what else is installed? |
33fa007 to
05f0429
Compare
4b47dae to
62d9fac
Compare
Owner
|
Thank you very much @henryiii. Yes I think we will have to wait until a new version of packaging is out and then "soft-validate" the field like it is done with trove-classifiers. |
abravalheri
approved these changes
Oct 14, 2024
Signed-off-by: Henry Schreiner <[email protected]>
Co-authored-by: Anderson Bravalheri <[email protected]>
a3b3ee1 to
9236307
Compare
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.
Starting PEP 639 support. It would be really nice to validate SPDX (wait for packaging?). I did make sure the incorrect combinations of license-files with non-string license is disallowed.
Close #70. I'm also adding support to SchemaStore's related file in SchemaStore/schemastore#4143.