Don't fail for complex license expressions #718
Closed
Conversation
This file contains 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
|
Thanks, but my preference is to allow only simple license expressions for now, and broaden it to valid compound expressions in the future, so we're expanding the set of what Flit accepts, not narrowing it (as discussed in #707). PyPI will validate license expressions on upload, but private indexes may not, and people may also just build packages without uploading them anywhere. If you really want to use compound expressions in the meantime, you can set the environment variable |
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.
Flit should support complex license expressions with
AND,ORorWITHand not raiseConfigError.We can skip the validation here (for now). PyPI will always validated uploads.