EnvGap
Inconsistent license information
envgap__mkleehammer__pyodbc-1314
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- In a clean container the reported failure did not reproduce, or the known fix did not make the project run.
02 / ENVIRONMENT RECIPE
- Base commit
f075e331a97db955d11938b49b593a260ffb5e1f- Manifest
pyproject.toml- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
mkleehammer/pyodbc #1314 · read the original issue
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)`.
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]