Closed stefan6419846 closed 4 months ago
When looking at the package source code, I observed that the package advertises two different variants of the MIT license: The "plain" MIT and the MIT-0 one.
While the license file and the source files use the MIT-0 license, both the pyproject.toml and the setup.py file refer to the "plain" MIT license: https://github.com/mkleehammer/pyodbc/blob/bc5b7c6f50f71aa776f881fafce95328338ed35e/setup.py#L58 https://github.com/mkleehammer/pyodbc/blob/bc5b7c6f50f71aa776f881fafce95328338ed35e/setup.py#L63 https://github.com/mkleehammer/pyodbc/blob/bc5b7c6f50f71aa776f881fafce95328338ed35e/pyproject.toml#L13 https://github.com/mkleehammer/pyodbc/blob/bc5b7c6f50f71aa776f881fafce95328338ed35e/pyproject.toml#L25 The correct SPDX identifier seems to be MIT-0, the correct trove classifier License :: OSI Approved :: MIT No Attribution License (MIT-0).
pyproject.toml
setup.py
MIT-0
License :: OSI Approved :: MIT No Attribution License (MIT-0)
Thanks for catching this. We'll update to MIT-0.
When looking at the package source code, I observed that the package advertises two different variants of the MIT license: The "plain" MIT and the MIT-0 one.
While the license file and the source files use the MIT-0 license, both the
pyproject.toml
and thesetup.py
file refer to the "plain" MIT license: https://github.com/mkleehammer/pyodbc/blob/bc5b7c6f50f71aa776f881fafce95328338ed35e/setup.py#L58 https://github.com/mkleehammer/pyodbc/blob/bc5b7c6f50f71aa776f881fafce95328338ed35e/setup.py#L63 https://github.com/mkleehammer/pyodbc/blob/bc5b7c6f50f71aa776f881fafce95328338ed35e/pyproject.toml#L13 https://github.com/mkleehammer/pyodbc/blob/bc5b7c6f50f71aa776f881fafce95328338ed35e/pyproject.toml#L25 The correct SPDX identifier seems to beMIT-0
, the correct trove classifierLicense :: OSI Approved :: MIT No Attribution License (MIT-0)
.