There are various LICENCE.txt files in subdirectories, which are
canonical. These LICENCE.txt files pre-date the PSF licence (or the
PSF!) even existing and this package has many many contributors from
this week back to last century, so re-licensing is almost impossible.
I don't think the PSF licence makes sense for projects not released by
the PSF - the closest would be a new custom license exactly like the PSF
license, but with some words change to make it clear the PSF isn't
releasing it.
If your lawyers aren't happy with the situation I'd love to hear their
advice for how it could be cleaned up.
Cheers,
Mark
On 5/04/2023 10:47 pm, Taras CIURIAK wrote:
Hi, can anyone please confirm the licensing status of the PyWin32
module? I'm under the impression that it's using the Python Software
Foundation License, as that's what it states on the Project page,
however I'm getting pushback from the powers that be because there's no
clearly obvious License.txt in the source:
/"unfortunately I do not believe the Python Software Foundation License
is still valid for this package. While in
https://pypi.org/project/pywin32/#description
<https://pypi.org/project/pywin32/#description> it does appear that it
is licensed under a Python Software Foundation license, the license has
unfortunately may have not (sic) been renewed for quite some time and is
not available on github."/
/
/
Thanks for any assistance you can provide to clarify..../Taras
_______________________________________________
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32
_______________________________________________
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32
