pyproject.toml: rework license information#827
Open
yegorich wants to merge 2 commits into
Open
Conversation
Don't use license info in the classifiers section define both license and license file via the new options. This resolves the following issues: *********************************************************************** Please use a simple string containing a SPDX expression for `project.license`. You can also use `project.license-files`. (Both options available on setuptools>=77.0.0). This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. *********************************************************************** *********************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: Public Domain See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. *********************************************************************** Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Author
|
There is another consideration: there is no "Public domain" license as an SPDX definition. So I had to create a custom tag. The closest definition would be CC0-1.0. |
Author
|
Do we need to bump setuptools to 77.0.0? |
Contributor
|
cclauss
force-pushed
the
fix-license-info
branch
from
022190b to
d463b26
Compare
Let's make sure that the `pyproject.toml` tools validate the proposed changes. * https://github.com/abravalheri/validate-pyproject/releases * https://github.com/tox-dev/pyproject-fmt/releases
cclauss
force-pushed
the
fix-license-info
branch
from
d463b26 to
1adbcdd
Compare
cclauss
approved these changes
Jun 11, 2026
cclauss
left a comment
cclauss
left a comment
Contributor
There was a problem hiding this comment.
@anandology @mekarpeles Can you please comment on whether we should choose the custom LicenseRef-Public-Domain-1.0 string conforming to the SPDX specification or the SPDX identifier CC0-1.0?
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.
Don't use license info in the classifiers section define both license and license file via the new options.
This resolves the following issues: