You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that individual parts of the pywin32 library are licensed under different terms, can you clarify what terms the isapi component is licensed under? Ideally this would involve adding a LICENSE.txt file to the isapi directory that is included within the wheel.
The text was updated successfully, but these errors were encountered:
Sorry for the delay and for the mess of the license situation. I've been vaguely handwaving for the last many years that everything in this repo is a "psf license" (eg, the badge in README) - but it's not clear to me that is actually a thing that makes sense for extensions. What exactly should I paste into a LICENSE file?
1. This LICENSE AGREEMENT is between the Python Software Foundation
("PSF"), and the Individual or Organization ("Licensee") accessing and
otherwise using this software ("Python")
as the first line seems wrong :)
So to answer your question for isapi: you can choose between any of the existing license terms you find in the repo, and/or a "psf 2.0" license.
Re a licence.txt and/or a (semi)-formal process of cleaning up this mess: I welcome any and all advice.
I understand that individual parts of the pywin32 library are licensed under different terms, can you clarify what terms the
isapi
component is licensed under? Ideally this would involve adding a LICENSE.txt file to the isapi directory that is included within the wheel.The text was updated successfully, but these errors were encountered: