Add SPDX license identifier #1989
Closed
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
| There hasn't been any activity here - closing it. Please fell free to reuse it. |
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.
Prepare for PEP 639 license expressions.
Setuptools
v77added full support for it. However that version requires Python>=3.9. Until3.8is dropped, the next best thing would be to use the legacylicense.textfield with the correct SPDX license identifier.All that's needed later would be
https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license-and-license-files
https://spdx.org/licenses/BSD-3-Clause.html