MISC: Add more precise license field to setup #733
Merged
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
|
I like it! Thank you ❤️ |
|
Fun fact: I did a couple of times an anlysis of all PyPI packages. That started because I was curious about the licenses (and got a bit out of hand ... a little bit like the fact that I'm not maintaining PyPDF2^^): https://medium.com/geekculture/the-state-of-pypi-2022-edition-d8e2cba9de2c if you're curious |
|
From PyPI: 🎉 |
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.
This PR makes the license metadata for the package more precise by utilizing the optional
Licensefield, so that people will see that it's theBSD-3-Clauselicense, and not just any old BSD license. Ideally we'd be able to use a classifier, but blocked on that front by pypa/trove-classifiers#17.