Use License Expressions in pyproject.toml #1111
Merged
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
csmarchbanks force-pushed the pep-639 branch 2 times, most recently from 2150f8f to 7bb3bf8 Compare 
With the release of PEP-639 the best practice for specifying the license is now to use a license expression in the license field and specify any license files in license-files rather than the table-based approach from PEP-621. Including the license in the classifiers is also no longer allowed when using PEP-639 and has been removed. Signed-off-by: Chris Marchbanks <csmarchbanks@gmail.com>
csmarchbanks commented May 29, 2025
| description = "Python client for the Prometheus monitoring system." | ||
| readme = "README.md" | ||
| license = { file = "LICENSE" } | ||
| license = "Apache-2.0 AND BSD-2-Clause" |
There was a problem hiding this comment.
BSD-2-Clause is from the decorators file we embed into this library.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
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.
With the release of PEP-639 the best practice for specifying the license is now to use a license expression in the license field and specify any license files in license-files rather than the table-based approach from PEP-621. Including the license in the classifiers is also no longer allowed when using PEP-639 and has been removed.