PyWin32 license

[da1910]

I see that pyWin32 is marked as manually excluded from license checking, with the logic that it's a PSF licensed package. This is definitely not the case, the code is a mess of conflicting license terms.

I'm not sure what we're using the license check action for, and what we claim it to be, but if anyone is using it as justification for legal purposes we need to be aware of the issues.

For example:
The adodbapi package is LGPL 2.1 - https://github.com/mhammond/pywin32/blob/main/adodbapi/adodbapi.py
The Scintilla vendored package is MIT - https://github.com/mhammond/pywin32/blob/main/Pythonwin/Scintilla/License.txt
The com package is old style BSD - https://github.com/mhammond/pywin32/blob/main/com/License.txt

[pyansys-automation]

Hello @jorgepiloto!
This issue has been open for over a year and has had no updates in the past 8 months. If it is still relevant, please provide an update. Otherwise, consider closing it to help keep the issue tracker clean.

If this issue needs to remain open, please comment below with @pyansys-automation never close issue to prevent it from being automatically closed.

If you want this repository to be excluded from this automated maintenance process, please let us know by filling in the opt-out request form.

[jorgepiloto]

Both MIT and BSD are compatible with our licensing strategy. Regarding LGPG, there is an on-going discussion in #1050.

[da1910]

Correct, the issue is more specific to the output from pip-licenses just being unreliable, it depends on what we are using the output for, but if it's actually used anywhere for legal compliance / reporting perspective then it is insufficient.