Repository navigation
The Unlicense not recognized as a license #6689
Description
- Poetry version: 1.2.1
- Python version: 3.8.10
- OS version and name: Linux Mint 20.3 Una
- pyproject.toml: https://gist.github.com/zahlman/a07c84135c4e9c0312ec11979ce307f6
- I am on the latest stable Poetry version, installed using a recommended method.
- I have searched the issues of this repo and believe that this is not a duplicate.
- I have consulted the FAQ and blog for any relevant entries or release notes.
- If an exception occurs when executing a command, I executed it again in debug mode (
-vvvoption) and have included the output below. (not applicable)
Issue
When I upload a package with the pyproject.toml linked above, the license is not properly identified.
Per https://spdx.org/licenses/, Unlicense is the identifier for The Unlicense, which is an OSI-approved (and FSF Free/Libre) license. My understanding from the Poetry documentation is that any SPDX identifier should work, and that a trove classifier should be generated for any license that has a corresponding classifier (which this one does).
Expected: on the corresponding PyPI project page, the License should be described as an OSI approved license, and the trove classifiers should include License :: OSI Approved :: The Unlicense (Unlicense).
Actual: no trove classifier is added for the license, and the meta section of the page states
License: Other/Proprietary License (Unlicense)
Activity
neersighted commentedon Oct 3, 2022
The Unlicense was not OSI approved when Poetry last synced the SPDX database. A re-sync of https://github.com/python-poetry/poetry-core/tree/main/src/poetry/core/spdx (there is tooling present to automate this) plus adding the classifier to
license.pyis fairly trivial and will resolve this.colindean commentedon Oct 4, 2022
I noted while searching for something similar that this seems to be handled in python-poetry/poetry-core#489
pmav99 commentedon Apr 26, 2023
on 1.4.2 this seems to have been fixed
stokito commentedon Apr 26, 2023
The Unlicense has some problems and you better to switch to some other well known license https://en.wikipedia.org/wiki/Unlicense
github-actions commentedon Feb 29, 2024
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.