-
Notifications
You must be signed in to change notification settings - Fork 88
MNT: Use SPDX license expression #107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
matthewfeickert
commented
Oct 29, 2025
- Use the recommended SPDX license expression string for the license identifier.
- c.f. https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license
- Remove the trove classifier as well, given DeprecationWarning.
- Additionally add long_description_content_type to pass 'twine check --strict'.
|
@tacaswell This addresses some metadata issues for getting cibuildwheel passing. |
* Use the recommended SPDX license expression string for the license identifier. - c.f. https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license * Remove the trove classifier as well, given DeprecationWarning. > ******************************************************************************** > Please consider removing the following classifiers in favor of a SPDX license expression: > License :: OSI Approved :: GNU Lesser General Public License v2 or later (LGPLv2+) > See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. > ******************************************************************************** * Additionally add long_description_content_type to pass 'twine check --strict'.
2b9ad87 to
744bdd5
Compare
| author='Mikhail Korobov', | ||
| author_email='kmike84@gmail.com', | ||
| license=LICENSE, | ||
| license="LGPL-2.1-or-later", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
This is mechanical "spell checking" of the license meta-data, but I would like to give @kmike and @superbobry a chance to weigh in before we merge this. |
👋 Ping @kmike @superbobry |
|
@tacaswell Do you have alternative ways of contacting them? |