Python-2.0.1 and CNRI-Python-GPL-Compatible
Max Mehl <[email protected]> Fri, 6 Mar 2026 13:47:47 +0000
| Newsgroups | gmane.comp.licenses.open-source.general |
|---|---|
| Message-ID | <AS8PR06MB75279CEF1A80B85B3707BCA5FB7AA@AS8PR06MB7527.eurprd06.prod.outlook.com> |
--===============1038474929596189087== Content-Language: en-GB Content-Type: multipart/alternative; boundary="_000_AS8PR06MB75279CEF1A80B85B3707BCA5FB7AAAS8PR06MB7527eurp_" Content-Transfer-Encoding: 7bit --_000_AS8PR06MB75279CEF1A80B85B3707BCA5FB7AAAS8PR06MB7527eurp_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi everyone, As requested by Nick, I would like point to an ongoing discussion on Python= licenses, affecting both OSI's and SPDX=92s realms, and request OSI=92s ap= proval of two licenses. As you know, the licensing history of Python is quite complex, and the curr= ent license consists of multiple other licenses representing the long histo= ry and the different =93ownerships=94 of the project (CWI, CNRI, BeOpen, PS= F). spdx/license-list-XML#2197<https://github.com/spdx/license-list-XML/iss= ues/2197> and an email to spdx-legal@<https://lists.spdx.org/g/Spdx-legal/t= opic/107252308> describe a bunch of intertwined problems around the identif= iers of components of Python licenses. Recently, OSI fixed some of those al= ready, thanks! Now, I wonder about the status of the license SPDX describes as Python-2.0.= 1<https://spdx.org/licenses/Python-2.0.1.html>. IIRC, the main difference b= etween Python-2.0<https://spdx.org/licenses/Python-2.0.html> and Python-2.0= .1 is in the CNRI part, making it GPL compatible (the =93Virginia clause=94= ). SPDX lists this updated sub-part as CNRI-Python-GPL-Compatible<https://s= pdx.org/licenses/CNRI-Python-GPL-Compatible.html>, a successor of CNRI-Pyth= on<https://spdx.org/licenses/CNRI-Python.html>. Since Python 1.6.1 and 2.0.1, Python releases have been licensed under Pyth= on-2.0.1 (and recently additionally 0BSD for its documentation), while Pyth= on-2.0 has only been used for Python 1.6 and 2.0. So modern CPython release= s would probably be best described as being licensed under "Python-2.0.1 AN= D 0BSD". But OSI only approved Python-2.0 as an Open Source license, as well as the = old CNRI-Python part. This is why I suggest OSI to approve Python-2.0.1 and= CNRI-Python-GPL-Compatible as Open Source licenses, and mark Python-2.0 an= d CNRI-Python as superseded. Is there any reason not to? Best, Max -- Max Mehl Open Source / Supply Chain Enterprise-Team Chief Technology Office (CTO) DB Systel GmbH / Deutsche Bahn Schedule a meeting: cal.com/mxmehl<https://cal.com/mxmehl> ________________________________ Pflichtangaben anzeigen<https://www.deutschebahn.com/pflichtangaben/2026030= 5> N=E4here Informationen zur Datenverarbeitung im DB-Konzern finden Sie hier:= https://www.deutschebahn.com/de/konzern/datenschutz --_000_AS8PR06MB75279CEF1A80B85B3707BCA5FB7AAAS8PR06MB7527eurp_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1= 252"> </head> <body> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> Hi everyone,</div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> As requested by Nick, I would like point to an ongoing discussion on Python= licenses, affecting both OSI's and SPDX=92s realms, and request OSI=92s ap= proval of two licenses.</div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> As you know, the licensing history of Python is quite complex, and the curr= ent license consists of multiple other licenses representing the long histo= ry and the different =93ownerships=94 of the project (CWI, CNRI, BeOpen, PS= F). <a href=3D"https://github.com/spdx/license-list-XML/issues/2197" data-outlo= ok-id=3D"c8d254e9-cda2-4b06-8db7-bce26d43e3bc"> spdx/license-list-XML#2197</a> and an <a href=3D"https://lists.spdx.or= g/g/Spdx-legal/topic/107252308" data-outlook-id=3D"fe102278-b8de-497c-ada5-= f66db752c1b7"> email to spdx-legal@</a> describe a bunch of intertwined problems arou= nd the identifiers of components of Python licenses. Recently, OSI fixed so= me of those already, thanks!</div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> Now, I wonder about the status of the license SPDX describes as <a href=3D"= https://spdx.org/licenses/Python-2.0.1.html" data-outlook-id=3D"8715974d-cf= 48-4f8a-804a-70c055157f8c"> Python-2.0.1</a>. IIRC, the main difference between <a href=3D"https://spdx= .org/licenses/Python-2.0.html" data-outlook-id=3D"91fa97a6-11f5-41c0-87e0-e= 557e08fc45c"> Python-2.0</a> and Python-2.0.1 is in the CNRI part, making it GPL com= patible (the =93Virginia clause=94). SPDX lists this updated sub-part as <a href=3D"https://spdx.org/licenses/CNRI-Python-GPL-Compatible.html" data-= outlook-id=3D"3567c9f9-2b49-47b0-81ea-244c5030e6b1"> CNRI-Python-GPL-Compatible</a>, a successor of <a href=3D"https://spdx.org/= licenses/CNRI-Python.html" data-outlook-id=3D"4e10b719-943a-4ba5-9168-f442c= 0eccf57"> CNRI-Python</a>.</div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> Since Python 1.6.1 and 2.0.1, Python releases have been licensed under Pyth= on-2.0.1 (and recently additionally 0BSD for its documentation), while Pyth= on-2.0 has only been used for Python 1.6 and 2.0. So modern CPython release= s would probably be best described as being licensed under "Python-2.0.1 AND 0BSD". </div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> But OSI only approved Python-2.0 as an Open Source license, as well as the = old CNRI-Python part. This is why I suggest OSI to approve <b>Python-2.0.1</b> and <b>CNRI-Python-GPL-Compatible</b> as Open= Source licenses, and mark Python-2.0 and CNRI-Python as superseded. Is the= re any reason not to?</div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> Best,</div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> Max </div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div id=3D"ms-outlook-mobile-signature" style=3D"color: inherit; background= -color: inherit;"> <p class=3D"MsoNormal" style=3D"margin: 0cm; font-family: Aptos, sans-serif= ; font-size: 11pt;"> <span style=3D"color: black;">-- </span></p> <p class=3D"MsoNormal" style=3D"margin: 0cm; font-family: Aptos, sans-serif= ; font-size: 11pt;"> <span style=3D"color: black;"><b>Max Mehl</b></span></p> <p class=3D"MsoNormal" style=3D"margin: 0cm; font-family: Aptos, sans-serif= ; font-size: 11pt;"> <span style=3D"color: black;">Open Source / Supply Chain</span></p> <p class=3D"MsoNormal" style=3D"margin: 0cm; font-family: Aptos, sans-serif= ; font-size: 11pt;"> <span style=3D"color: black;">Enterprise-Team Chief Technology Office (CTO)= </span></p> <p class=3D"MsoNormal" style=3D"margin: 0cm; font-family: Aptos, sans-serif= ; font-size: 11pt;"> <span style=3D"color: black;">DB Systel GmbH / Deutsche Bahn</span></p> <p class=3D"MsoNormal" style=3D"margin: 0cm; font-family: Aptos, sans-serif= ; font-size: 11pt;"> <span style=3D"color: black;"><br> </span></p> <p class=3D"MsoNormal" style=3D"margin: 0cm; font-family: Aptos, sans-serif= ; font-size: 11pt;"> <span style=3D"color: black;">Schedule a meeting: <a href=3D"https://cal.co= m/mxmehl" data-outlook-id=3D"4bf758be-12c8-40e6-b18a-99718d15ab49" style=3D= "margin-top: 0px; margin-bottom: 0px;"> cal.com/mxmehl</a></span></p> <p class=3D"MsoNormal" style=3D"margin: 0cm; font-family: Aptos, sans-serif= ; font-size: 11pt;"> <span style=3D"color: black;"><br> </span></p> </div> <br> <hr> <br> <a href=3D"https://www.deutschebahn.com/pflichtangaben/20260305">Pflichtang= aben anzeigen</a><br> <br> N=E4here Informationen zur Datenverarbeitung im DB-Konzern finden Sie hier:= <a href=3D"https://www.deutschebahn.com/de/konzern/datenschutz"> https://www.deutschebahn.com/de/konzern/datenschutz</a> </body> </html> --_000_AS8PR06MB75279CEF1A80B85B3707BCA5FB7AAAS8PR06MB7527eurp_-- --===============1038474929596189087== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KVGhlIG9waW5p b25zIGV4cHJlc3NlZCBpbiB0aGlzIGVtYWlsIGFyZSB0aG9zZSBvZiB0aGUgc2VuZGVyIGFuZCBu b3QgbmVjZXNzYXJpbHkgdGhvc2Ugb2YgdGhlIE9wZW4gU291cmNlIEluaXRpYXRpdmUuIE9mZmlj aWFsIHN0YXRlbWVudHMgYnkgdGhlIE9wZW4gU291cmNlIEluaXRpYXRpdmUgd2lsbCBiZSBzZW50 IGZyb20gYW4gb3BlbnNvdXJjZS5vcmcgZW1haWwgYWRkcmVzcy4KCkxpY2Vuc2UtZGlzY3VzcyBt YWlsaW5nIGxpc3QKTGljZW5zZS1kaXNjdXNzQGxpc3RzLm9wZW5zb3VyY2Uub3JnCmh0dHA6Ly9s aXN0cy5vcGVuc291cmNlLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2xpY2Vuc2UtZGlzY3Vzc19saXN0 cy5vcGVuc291cmNlLm9yZwo= --===============1038474929596189087==--