Python licenses

Jilayne Lovejoy <Jlovejoy@...>

I agree these licenses are a bit redundant seeming and not well differentiated.  However, I think when a license has been approved by the OSI, we need to just stick with the license name they use.  Although Tom’s list here is better than what we see “in the field,” I don’t think we should include which versions of the software the license covers (not sure if that is what you were suggesting, anyway).  


I have updated the License List (from this morning) to have the two python OSI-approved licenses and checked that the license name listed matches the name OSI uses.  If someone thinks the other iterations need to be added, let me know.  




From: Tom Incorvia [mailto:tom.incorvia@...]
Sent: Thursday, October 21, 2010 8:51 AM
To: Tom "spot" Callaway
Cc: Jilayne Lovejoy; kate.stewart@...; spdx@...
Subject: RE: License List spreadsheet v1.1


FYI, I did a compare of Python 3.2 LICENSE to the much earlier 2.0.1 AFTER removing the history information – so the compare started with the statement “TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON”. 


The licenses are the same other than adding to the list of copyright years and changing the title “CWI PERMISSIONS STATEMENT AND DISCLAIMER” TO “CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2”.  I have attached the compare.


I also noticed that the license link for particular versions of the Python software don’t always match.  For instance the link links to a license titled 2.4.4 license.  Similarly the URL for 3.0.1 points to a license titled 2.6.1.  There are others.


Between versions 2.4.4 and 2.5 “Version 2” is added to the license.  But the changes continue to be limited to extensions of the copyright years.


I believe that the discrete licenses are:




-          Python Version 1 (Covers Python after 1.6.1 and prior to 2.5)

-          Python Version 2 (Covers Python 2.5 and after)


Tom W, what do you think – some of the specificity in versions and release is removed as the licenses get newer.  I have not looked for language re self-superseding.






Tom Incorvia


Direct:  (512) 340-1336

Mobile: (408) 499 6850


-----Original Message-----
From: Tom "spot" Callaway [mailto:tcallawa@...]
Sent: Wednesday, October 20, 2010 2:03 PM
To: Tom Incorvia
Cc: Jilayne Lovejoy; kate.stewart@...; spdx@...
Subject: Re: License List spreadsheet v1.1


On 10/20/2010 02:56 PM, Tom Incorvia wrote:

> -          The Python license may have versions – I am not certain --

> they take the time to restate the license with each release – however, I

> comparisons of some of the “official licenses” and they were the same.

> Anyway, we will need to dig into Python a bit in terms of versioning and

> relationship to CNRI – I don’t have the bandwidth for this right now,

> but hopefully there is someone on the team who is deep into Python licensing


To the best of my understanding, there have been several different

Python license versions, but the licenses are self-superseding, in that

as new versions arrive, they automatically apply.





This message has been scanned for viruses by MailController -