<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Max:</p>
<p>If you think the newer version of the Python license ought to be
approved by the OSI, someone needs to submit it through the
license approval process, described here:
<a class="moz-txt-link-freetext" href="https://opensource.org/licenses/review-process">https://opensource.org/licenses/review-process</a></p>
<p>Given that it sounds like 2.0.1 is now being used by Python, and
2.0 is only a legacy of older versions, I'd suggest that if
submitted, at the same time 2.0 be "Voluntarily Retired" as have
many other licenses that have been superceded by newer versions
(see the list here:
<a class="moz-txt-link-freetext" href="https://opensource.org/licenses?categories=superseded%2Cvoluntarily-retired">https://opensource.org/licenses?categories=superseded%2Cvoluntarily-retired</a>);
if it is not, 2.0 will likely be tagged (if 2.0.1 is approved) as
superseded, like these licenses:
<a class="moz-txt-link-freetext" href="https://opensource.org/licenses?categories=superseded">https://opensource.org/licenses?categories=superseded</a> Same comment
for the newer CNRI license versus the old one.</p>
<p>I would suggest that someone from the Python community (if you
aren't one already) do the submission, if that result is indeed
desired. The review process requirements are in the link above.</p>
<p>*This is no commentary on the approvability of the 2.0.1. or new
CNRI license, which I haven't read, but just a general comment on
how the result you want might be accomplished.</p>
<p>McCoy Smith</p>
<div class="moz-cite-prefix">On 3/16/2026 5:46 PM, Pamela Chestek
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:33851f01-1e41-4900-aeaa-22580c6a0318@chesteklegal.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>I don't see a reason. The OSI generally only reacts to requests
for license approval, it doesn't generally approve licenses
without them being submitted. I'm assuming it hasn't be approved
just because no one has asked for it before.</p>
<p>Pam</p>
<div class="moz-signature">Pamela S. Chestek<br>
Chestek Legal<br>
4641 Post St.<br>
Unit 4316<br>
El Dorado Hills, CA 95762<br>
+1 919-800-8033<br>
<a class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:pamela@chesteklegal.com" moz-do-not-send="true">pamela@chesteklegal.com</a><br>
<a class="moz-txt-link-abbreviated"
href="http://www.chesteklegal.com" moz-do-not-send="true">www.chesteklegal.com</a><br>
<br>
<br>
</div>
<div class="moz-cite-prefix">On 3/6/2026 5:47 AM, Max Mehl wrote:<br>
</div>
<blockquote type="cite"
cite="mid:AS8PR06MB75279CEF1A80B85B3707BCA5FB7AA@AS8PR06MB7527.eurprd06.prod.outlook.com">
<meta http-equiv="Content-Type"
content="text/html; charset=UTF-8">
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi everyone,</div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; 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\u2019s
realms, and request OSI\u2019s approval of two licenses.</div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
As you know, the licensing history of Python is quite complex,
and the current license consists of multiple other licenses
representing the long history and the different \u201cownerships\u201d
of the project (CWI, CNRI, BeOpen, PSF). <a
href="https://github.com/spdx/license-list-XML/issues/2197"
data-outlook-id="c8d254e9-cda2-4b06-8db7-bce26d43e3bc"
moz-do-not-send="true"> spdx/license-list-XML#2197</a> and
an <a
href="https://lists.spdx.org/g/Spdx-legal/topic/107252308"
data-outlook-id="fe102278-b8de-497c-ada5-f66db752c1b7"
moz-do-not-send="true"> email to spdx-legal@</a> describe a
bunch of intertwined problems around the identifiers of
components of Python licenses. Recently, OSI fixed some of
those already, thanks!</div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Now, I wonder about the status of the license SPDX describes
as <a href="https://spdx.org/licenses/Python-2.0.1.html"
data-outlook-id="8715974d-cf48-4f8a-804a-70c055157f8c"
moz-do-not-send="true"> Python-2.0.1</a>. IIRC, the main
difference between <a
href="https://spdx.org/licenses/Python-2.0.html"
data-outlook-id="91fa97a6-11f5-41c0-87e0-e557e08fc45c"
moz-do-not-send="true"> Python-2.0</a> and Python-2.0.1 is
in the CNRI part, making it GPL compatible (the \u201cVirginia
clause\u201d). SPDX lists this updated sub-part as <a
href="https://spdx.org/licenses/CNRI-Python-GPL-Compatible.html"
data-outlook-id="3567c9f9-2b49-47b0-81ea-244c5030e6b1"
moz-do-not-send="true"> CNRI-Python-GPL-Compatible</a>, a
successor of <a
href="https://spdx.org/licenses/CNRI-Python.html"
data-outlook-id="4e10b719-943a-4ba5-9168-f442c0eccf57"
moz-do-not-send="true"> CNRI-Python</a>.</div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Since Python 1.6.1 and 2.0.1, Python releases have been
licensed under Python-2.0.1 (and recently additionally 0BSD
for its documentation), while Python-2.0 has only been used
for Python 1.6 and 2.0. So modern CPython releases would
probably be best described as being licensed under
"Python-2.0.1 AND 0BSD". </div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; 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 there any reason not to?</div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Best,</div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Max </div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="ms-outlook-mobile-signature"
style="color: inherit; background-color: inherit;">
<p class="MsoNormal"
style="margin: 0cm; font-family: Aptos, sans-serif; font-size: 11pt;"> <span
style="color: black;">-- </span></p>
<p class="MsoNormal"
style="margin: 0cm; font-family: Aptos, sans-serif; font-size: 11pt;"> <span
style="color: black;"><b>Max Mehl</b></span></p>
<p class="MsoNormal"
style="margin: 0cm; font-family: Aptos, sans-serif; font-size: 11pt;"> <span
style="color: black;">Open Source / Supply Chain</span></p>
<p class="MsoNormal"
style="margin: 0cm; font-family: Aptos, sans-serif; font-size: 11pt;"> <span
style="color: black;">Enterprise-Team Chief Technology
Office (CTO)</span></p>
<p class="MsoNormal"
style="margin: 0cm; font-family: Aptos, sans-serif; font-size: 11pt;"> <span
style="color: black;">DB Systel GmbH / Deutsche Bahn</span></p>
<p class="MsoNormal"
style="margin: 0cm; font-family: Aptos, sans-serif; font-size: 11pt;"> <span
style="color: black;"><br>
</span></p>
<p class="MsoNormal"
style="margin: 0cm; font-family: Aptos, sans-serif; font-size: 11pt;"> <span
style="color: black;">Schedule a meeting: <a
href="https://cal.com/mxmehl"
data-outlook-id="4bf758be-12c8-40e6-b18a-99718d15ab49"
style="margin-top: 0px; margin-bottom: 0px;"
moz-do-not-send="true"> cal.com/mxmehl</a></span></p>
<p class="MsoNormal"
style="margin: 0cm; font-family: Aptos, sans-serif; font-size: 11pt;"> <span
style="color: black;"><br>
</span></p>
</div>
<br>
<hr> <br>
<a href="https://www.deutschebahn.com/pflichtangaben/20260305"
moz-do-not-send="true">Pflichtangaben anzeigen</a><br>
<br>
Nähere Informationen zur Datenverarbeitung im DB-Konzern finden
Sie hier: <a
href="https://www.deutschebahn.com/de/konzern/datenschutz"
moz-do-not-send="true" class="moz-txt-link-freetext">
https://www.deutschebahn.com/de/konzern/datenschutz</a> <br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Official statements by the Open Source Initiative will be sent from an opensource.org email address.
License-discuss mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:License-discuss@lists.opensource.org"
moz-do-not-send="true">License-discuss@lists.opensource.org</a>
<a class="moz-txt-link-freetext"
href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org"
moz-do-not-send="true">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a>
</pre>
</blockquote>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Official statements by the Open Source Initiative will be sent from an opensource.org email address.
License-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:License-discuss@lists.opensource.org">License-discuss@lists.opensource.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a>
</pre>
</blockquote>
</body>
</html>