Re: Python-2.0.1 and CNRI-Python-GPL-Compatible

--===============6600522015036678159==
Content-Type: multipart/alternative;
	boundary="=_ace9577a-acb7-493c-80b9-59c8e8dcf695"
Content-Transfer-Encoding: 7bit

--=_ace9577a-acb7-493c-80b9-59c8e8dcf695
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Max,=20

I came around this thread and realized that the situation of the Python lic=
enses on spdx.org and on the OSI site is quite a mess.=20

I'm still in the process of sorting, but a current breakdown:=20

As far as I can see, the Python license on the OSI site ( [ https://opensou=
rce.org/license/Python-2.0 | https://opensource.org/license/Python-2.0 ] ) =
was never used in any Python release.=20
It is a strange bastard of the license texts of Python 2.5, but with the CN=
RI license part (for Python 1.6.1) *replaced* with an very early draft of t=
he license (from Python 1.6 beta1), which was never used in any public rele=
ase.=20

I'm pretty sure this license text is a copy & paste error. The same problem=
 also affects the "Python-2.0" license on SPDX ( [ https://spdx.org/license=
s/Python-2.0.html | https://spdx.org/licenses/Python-2.0.html ] ).=20

The Python 2.5 license ( [ https://www.python.org/download/releases/2.5/lic=
ense/ | https://www.python.org/download/releases/2.5/license/ ] ) includes =
the CNRI OPEN SOURCE LICENSE AGREEMENT (for Python 1.6).=20

I don't know about the implications, but the CNRI license agreement for Pyt=
hon 1.6 beta1 differed significantly from the license for 1.6.1. I'm pretty=
 sure that the license for=20
1.6b1 was not compatible with the GPL.=20

It's very strange to see that a search for "CNRI OPEN SOURCE LICENSE AGREEM=
ENT (for Python 1.6b1)" gives so many hits, if you know that this text was =
never included in any public Python release.=20

Conclusion: I think it's very reasonable to submit the current Python licen=
se for approval.=20

More details:=20

Historically, the Python LICENSE file is a collection of different license =
agreements that cover different parts of the code. Also, until recently, th=
e text of the license was updated for nearly every release (e.g. to append =
the year of the release). Only recently the PSF has adopted a scheme where =
the text of the license stays the same (still, the LICENSE file is updated)=
.=20

So what the SPDX calls the "Python License 2.0.1" is in fact simply the lic=
ense used in Python 2.0.1.=20
To make things more complicated, what SPDX calls the "Python License 2.0" i=
s not the license used in Python 2.0, but the license used e.g. in Python 2=
.5.=20

But for some reason, the section with the CNRI license agreement for Python=
 1.6 was replaced with the CNRI license agreement used in Python 1.6 beta1.=
=20

Strange thing is that this beta1 release of 1.6 had license terms that were=
 never before and never after used: The public release of Python 1.6 had a =
significantly different license and then again in Python 1.6.1 the license =
was changed again (to make it compatible with the GPL, again):=20
- License of Python 1.6b1: [ http://hdl.handle.net/1895.22/1011 | http://hd=
l.handle.net/1895.22/1011 ]=20
- License of Python 1.6: [ http://hdl.handle.net/1895.22/1012 | http://hdl.=
handle.net/1895.22/1012 ]=20
- License of Python 1.6.1: [ http://hdl.handle.net/1895.22/1013 | http://hd=
l.handle.net/1895.22/1013 ]=20

Best regards,=20
Gregor Hoffleit=20

> Von: "Max Mehl" <[email protected]>
> An: "license-discuss" <[email protected]>
> Gesendet: Freitag, 20. M=C3=A4rz 2026 17:18:29
> Betreff: Re: [License-discuss] Python-2.0.1 and CNRI-Python-GPL-Compatibl=
e

> Hi all,

> Thanks for the additional comments. I=E2=80=99ve met Deb (ED of PSF) in B=
erlin this week
> and she was fine with me submitting both licenses, provided I Cc her in t=
he
> submission emails.

> Consequently, I=E2=80=99ve opened two separate threads on license-review@=
.

> Best,
> Max

> From: License-discuss <[email protected]> on b=
ehalf
> of McCoy Smith <[email protected]>
> Date: Tuesday, 17. March 2026 at 15:34
> To: [email protected] <[email protected]=
e.org>
> Subject: Re: [License-discuss] Python-2.0.1 and CNRI-Python-GPL-Compatibl=
e

> Max:

> 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, des=
cribed
> here: [ https://opensource.org/licenses/review-process |
> https://opensource.org/licenses/review-process ]

> Given that it sounds like 2.0.1 is now being used by Python, and 2.0 is o=
nly 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 super=
ceded
> by newer versions (see the list here: [
> https://opensource.org/licenses?categories=3Dsuperseded%2Cvoluntarily-ret=
ired |
> https://opensource.org/licenses?categories=3Dsuperseded%2Cvoluntarily-ret=
ired ] );
> if it is not, 2.0 will likely be tagged (if 2.0.1 is approved) as superse=
ded,
> like these licenses: [ https://opensource.org/licenses?categories=3Dsuper=
seded |
> https://opensource.org/licenses?categories=3Dsuperseded ] Same comment fo=
r the
> newer CNRI license versus the old one.

> 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.

> *This is no commentary on the approvability of the 2.0.1. or new CNRI lic=
ense,
> which I haven't read, but just a general comment on how the result you wa=
nt
> might be accomplished.

> McCoy Smith
> On 3/16/2026 5:46 PM, Pamela Chestek wrote:

>> I don't see a reason. The OSI generally only reacts to requests for lice=
nse
>> approval, it doesn't generally approve licenses without them being submi=
tted.
>> I'm assuming it hasn't be approved just because no one has asked for it =
before.

>> Pam
>> Pamela S. Chestek
>> Chestek Legal
>> 4641 Post St.
>> Unit 4316
>> El Dorado Hills, CA 95762
>> +1 919-800-8033
>> [ mailto:[email protected] | [email protected] ]
>> [ http://www.chesteklegal.com/ | www.chesteklegal.com ]

>> On 3/6/2026 5:47 AM, Max Mehl wrote:

>>> Hi everyone,

>>> As requested by Nick, I would like point to an ongoing discussion on Py=
thon
>>> licenses, affecting both OSI's and SPDX=E2=80=99s realms, and request O=
SI=E2=80=99s approval of
>>> two licenses.

>>> As you know, the licensing history of Python is quite complex, and the =
current
>>> license consists of multiple other licenses representing the long histo=
ry and
>>> the different =E2=80=9Cownerships=E2=80=9D of the project (CWI, CNRI, B=
eOpen, PSF). [
>>> https://github.com/spdx/license-list-XML/issues/2197 |
>>> spdx/license-list-XML#2197 ] and an [
>>> https://lists.spdx.org/g/Spdx-legal/topic/107252308 |
>>> email to spdx-legal@ ] describe a bunch of intertwined problems around =
the
>>> identifiers of components of Python licenses. Recently, OSI fixed some =
of those
>>> already, thanks!

>>> Now, I wonder about the status of the license SPDX describes as [
>>> https://spdx.org/licenses/Python-2.0.1.html |
>>> Python-2.0.1 ] . IIRC, the main difference between [
>>> https://spdx.org/licenses/Python-2.0.html |
>>> Python-2.0 ] and Python-2.0.1 is in the CNRI part, making it GPL compat=
ible (the
>>> =E2=80=9CVirginia clause=E2=80=9D). SPDX lists this updated sub-part as=
 [
>>> https://spdx.org/licenses/CNRI-Python-GPL-Compatible.html |
>>> CNRI-Python-GPL-Compatible ] , a successor of [
>>> https://spdx.org/licenses/CNRI-Python.html |
>>> CNRI-Python ] .

>>> 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), wh=
ile
>>> 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 "Pyth=
on-2.0.1
>>> AND 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=
 and
>>> 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: [ https://cal.com/mxmehl |
>>> cal.com/mxmehl ]

>>> [ https://www.deutschebahn.com/pflichtangaben/20260305 | Pflichtangaben=
 anzeigen
>>> ]

>>> N=C3=A4here Informationen zur Datenverarbeitung im DB-Konzern finden Si=
e hier: [
>>> https://www.deutschebahn.com/de/konzern/datenschutz |
>>> https://www.deutschebahn.com/de/konzern/datenschutz ]
>>> _______________________________________________
>>> The opinions expressed in this email are those of the sender and not ne=
cessarily
>>> those of the Open Source Initiative. Official statements by the Open So=
urce
>>> Initiative will be sent from an opensource.org email address.

>>> License-discuss mailing list [ mailto:[email protected].=
org |
>>> [email protected] ] [
>>> http://lists.opensource.org/mailman/listinfo/license-discuss_lists.open=
source.org
>>> |
>>> http://lists.opensource.org/mailman/listinfo/license-discuss_lists.open=
source.org
>>> ]

>> _______________________________________________
>> The opinions expressed in this email are those of the sender and not nec=
essarily
>> those of the Open Source Initiative. Official statements by the Open Sou=
rce
>> Initiative will be sent from an opensource.org email address.

>> License-discuss mailing list [ mailto:[email protected]=
rg |
>> [email protected] ] [
>> http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opens=
ource.org
>> |
>> http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opens=
ource.org
>> ]

> [ https://www.deutschebahn.com/pflichtangaben/20260319 | Pflichtangaben a=
nzeigen
> ]

> N=C3=A4here Informationen zur Datenverarbeitung im DB-Konzern finden Sie =
hier: [
> https://www.deutschebahn.com/de/konzern/datenschutz |
> https://www.deutschebahn.com/de/konzern/datenschutz ]
> _______________________________________________
> The opinions expressed in this email are those of the sender and not nece=
ssarily
> those of the Open Source Initiative. Official statements by the Open Sour=
ce
> Initiative will be sent from an opensource.org email address.

> License-discuss mailing list
> [email protected]
> http://lists.opensource.org/mailman/listinfo/license-discuss_lists.openso=
urce.org

--=_ace9577a-acb7-493c-80b9-59c8e8dcf695
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"font-family: arial, helvetica, sans-serif; font-s=
ize: 12pt; color: #000000"><div>Hi Max,</div><div><br data-mce-bogus=3D"1">=
</div><div>I came around this thread and realized that the situation of the=
 Python licenses on spdx.org and on the OSI site is quite a mess.</div><div=
><br data-mce-bogus=3D"1"></div><div>I'm still in the process of sorting, b=
ut a current breakdown:</div><div><br data-mce-bogus=3D"1"></div><div><div>=
As far as I can see, the Python license on the OSI site&nbsp;(<a href=3D"ht=
tps://opensource.org/license/Python-2.0">https://opensource.org/license/Pyt=
hon-2.0</a>) was never used in any Python release.</div><div>It is a strang=
e bastard of the license texts of Python 2.5, but with the CNRI license par=
t (for Python 1.6.1) *replaced* with an very early draft of the license (fr=
om Python 1.6 beta1), which was never used in any public release.</div><div=
><br data-mce-bogus=3D"1"></div><div>I'm pretty sure this license text is a=
 copy &amp; paste error. The same problem also affects the "Python-2.0" lic=
ense on SPDX&nbsp;(<a href=3D"https://spdx.org/licenses/Python-2.0.html" da=
ta-mce-href=3D"https://spdx.org/licenses/Python-2.0.html">https://spdx.org/=
licenses/Python-2.0.html</a>).</div><div><br data-mce-bogus=3D"1"></div><di=
v>The Python 2.5 license (<a href=3D"https://www.python.org/download/releas=
es/2.5/license/" data-mce-href=3D"https://www.python.org/download/releases/=
2.5/license/">https://www.python.org/download/releases/2.5/license/</a>) in=
cludes the CNRI OPEN SOURCE LICENSE AGREEMENT (for Python 1.6).</div><div><=
br data-mce-bogus=3D"1"></div><div>I don't know about the implications, but=
 the CNRI license agreement for Python 1.6 beta1 differed significantly fro=
m the license for 1.6.1. I'm pretty sure that the license for </div><div>1.=
6b1 was not compatible with the GPL.</div><div><br data-mce-bogus=3D"1"></d=
iv><div><br data-mce-bogus=3D"1"></div><div>It's very strange to see that a=
 search for "CNRI OPEN SOURCE LICENSE AGREEMENT (for Python 1.6b1)" gives s=
o many hits, if you know that this text was never included in any public Py=
thon release.</div></div><div><br data-mce-bogus=3D"1"></div><div><br data-=
mce-bogus=3D"1"></div><div>Conclusion: I think it's very reasonable to subm=
it the current Python license for approval.</div><div><br data-mce-bogus=3D=
"1"></div><div><br data-mce-bogus=3D"1"></div><div><br data-mce-bogus=3D"1"=
></div><div><br data-mce-bogus=3D"1"></div><div>More details:</div><div><br=
 data-mce-bogus=3D"1"></div><div>Historically, the Python LICENSE file is a=
 collection of different license agreements that cover different parts of t=
he code. Also, until recently, the text of the license was updated for near=
ly every release (e.g. to append the year of the release). Only recently th=
e PSF has adopted a scheme where the text of the license stays the same (st=
ill, the LICENSE file is updated).</div><div><br data-mce-bogus=3D"1"></div=
><div>So what the SPDX calls the "Python License 2.0.1" is in fact simply t=
he license used in Python 2.0.1.</div><div>To make things more complicated,=
 what SPDX calls the "Python License 2.0" is not the license used in Python=
 2.0, but the license used e.g. in Python 2.5.</div><div><br data-mce-bogus=
=3D"1"></div><div>But for some reason, the section with the CNRI license ag=
reement for Python 1.6 was replaced with the CNRI license agreement used in=
 Python 1.6 beta1.</div><div><br data-mce-bogus=3D"1"></div><div><div>Stran=
ge thing is that this beta1 release of 1.6 had license terms that were neve=
r before and never after used: The public release of Python 1.6 had a signi=
ficantly different license and then again in Python 1.6.1 the license was c=
hanged again (to make it compatible with the GPL, again):</div><div>- Licen=
se of Python 1.6b1: <a href=3D"http://hdl.handle.net/1895.22/1011" data-mce=
-href=3D"http://hdl.handle.net/1895.22/1011">http://hdl.handle.net/1895.22/=
1011</a><br data-mce-bogus=3D"1"></div><div>- License of Python 1.6: <a hre=
f=3D"http://hdl.handle.net/1895.22/1012" data-mce-href=3D"http://hdl.handle=
.net/1895.22/1012">http://hdl.handle.net/1895.22/1012</a><br data-mce-bogus=
=3D"1"></div><div>- License of Python 1.6.1: <a href=3D"http://hdl.handle.n=
et/1895.22/1013" data-mce-href=3D"http://hdl.handle.net/1895.22/1013">http:=
//hdl.handle.net/1895.22/1013</a><br data-mce-bogus=3D"1"></div><div><br da=
ta-mce-bogus=3D"1"></div><div><br data-mce-bogus=3D"1"></div></div><div><br=
 data-mce-bogus=3D"1"></div><div><br data-mce-bogus=3D"1"></div><div>Best r=
egards,</div><div>&nbsp; &nbsp; Gregor Hoffleit</div><div><br data-mce-bogu=
s=3D"1"></div><div><br data-mce-bogus=3D"1"></div><div><br></div><div><br><=
/div><hr id=3D"zwchr" data-marker=3D"__DIVIDER__"><div data-marker=3D"__HEA=
DERS__"><blockquote style=3D"border-left:2px solid #1010FF;margin-left:5px;=
padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decor=
ation:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>Von: =
</b>"Max Mehl" &lt;[email protected]&gt;<br><b>An: </b>"license-dis=
cuss" &lt;[email protected]&gt;<br><b>Gesendet: </b>Frei=
tag, 20. M=C3=A4rz 2026 17:18:29<br><b>Betreff: </b>Re: [License-discuss] P=
ython-2.0.1 and CNRI-Python-GPL-Compatible<br></blockquote></div><div data-=
marker=3D"__QUOTED_TEXT__"><blockquote style=3D"border-left:2px solid #1010=
FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-styl=
e:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-s=
ize:12pt;"><div style=3D"direction:ltr;font-family:'aptos' , 'arial' , 'hel=
vetica' , sans-serif;font-size:12pt;color:rgb( 0 , 0 , 0 )">
Hi all,</div>
<div style=3D"direction:ltr;font-family:'aptos' , 'arial' , 'helvetica' , s=
ans-serif;font-size:12pt;color:rgb( 0 , 0 , 0 )">
<br>
</div>
<div style=3D"direction:ltr;font-family:'aptos' , 'arial' , 'helvetica' , s=
ans-serif;font-size:12pt;color:rgb( 0 , 0 , 0 )">
Thanks for the additional comments. I=E2=80=99ve met Deb (ED of PSF) in Ber=
lin this week and she was fine with me submitting both licenses, provided I=
 Cc her in the submission emails.</div>
<div style=3D"direction:ltr;font-family:'aptos' , 'arial' , 'helvetica' , s=
ans-serif;font-size:12pt;color:rgb( 0 , 0 , 0 )">
<br>
</div>
<div style=3D"direction:ltr;font-family:'aptos' , 'arial' , 'helvetica' , s=
ans-serif;font-size:12pt;color:rgb( 0 , 0 , 0 )">
Consequently, I=E2=80=99ve opened two separate threads on license-review@.<=
/div>
<div style=3D"direction:ltr;font-family:'aptos' , 'arial' , 'helvetica' , s=
ans-serif;font-size:12pt;color:rgb( 0 , 0 , 0 )">
<br>
</div>
<div style=3D"direction:ltr;font-family:'aptos' , 'arial' , 'helvetica' , s=
ans-serif;font-size:12pt;color:rgb( 0 , 0 , 0 )">
Best,</div>
<div style=3D"direction:ltr;font-family:'aptos' , 'arial' , 'helvetica' , s=
ans-serif;font-size:12pt;color:rgb( 0 , 0 , 0 )">
Max&nbsp;</div>
<div style=3D"direction:ltr;font-family:'aptos' , 'arial' , 'helvetica' , s=
ans-serif;font-size:12pt;color:rgb( 0 , 0 , 0 )">
<br>
</div>
<div style=3D"direction:ltr;font-family:'aptos' , 'arial' , 'helvetica' , s=
ans-serif;font-size:12pt;color:rgb( 0 , 0 , 0 )">
<br>
</div>
<div id=3D"mail-editor-reference-message-container" style=3D"color:inherit;=
background-color:inherit">
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr">
</div>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"te=
xt-align:left;padding:3pt 0in 0in;border-width:1pt medium medium;border-sty=
le:solid none none;border-color:rgb( 181 , 196 , 223 );font-family:'aptos';=
font-size:12pt;color:black">
<b>From: </b>License-discuss &lt;[email protected]=
rg&gt; on behalf of McCoy Smith &lt;[email protected]&gt;<br>
<b>Date: </b>Tuesday, 17. March 2026 at 15:34<br>
<b>To: </b>[email protected] &lt;[email protected]=
pensource.org&gt;<br>
<b>Subject: </b>Re: [License-discuss] Python-2.0.1 and CNRI-Python-GPL-Comp=
atible<br>
<br>
</div>
<p class=3D"ms-outlook-mobile-reference-message skipProofing">Max:</p>
<p class=3D"ms-outlook-mobile-reference-message skipProofing">If you think =
the newer version of the Python license ought to be approved by the OSI, so=
meone needs to submit it through the license approval process, described he=
re:
<a href=3D"https://opensource.org/licenses/review-process" style=3D"margin-=
top:0px;margin-bottom:0px" target=3D"_blank" rel=3D"nofollow noopener noref=
errer">
https://opensource.org/licenses/review-process</a><br data-mce-bogus=3D"1">=
</p>
<p class=3D"ms-outlook-mobile-reference-message skipProofing">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 "Vo=
luntarily Retired" as have many other
 licenses that have been superceded by newer versions (see the list here: <=
a href=3D"https://opensource.org/licenses?categories=3Dsuperseded%2Cvolunta=
rily-retired" style=3D"margin-top:0px;margin-bottom:0px" target=3D"_blank" =
rel=3D"nofollow noopener noreferrer">
https://opensource.org/licenses?categories=3Dsuperseded%2Cvoluntarily-retir=
ed</a>); if it is not, 2.0 will likely be tagged (if 2.0.1 is approved) as =
superseded, like these licenses:
<a href=3D"https://opensource.org/licenses?categories=3Dsuperseded" style=
=3D"margin-top:0px;margin-bottom:0px" target=3D"_blank" rel=3D"nofollow noo=
pener noreferrer">
https://opensource.org/licenses?categories=3Dsuperseded</a>&nbsp;Same comme=
nt for the newer CNRI license versus the old one.</p>
<p class=3D"ms-outlook-mobile-reference-message skipProofing">I would sugge=
st that someone from the Python community (if you aren't one already) do th=
e submission, if that result is indeed desired. The review process requirem=
ents are in the link above.</p>
<p class=3D"ms-outlook-mobile-reference-message skipProofing">*This is no c=
ommentary on the approvability of the 2.0.1. or new CNRI license, which I h=
aven't read, but just a general comment on how the result you want might be=
 accomplished.</p>
<p class=3D"ms-outlook-mobile-reference-message skipProofing">McCoy Smith</=
p>
<div class=3D"moz-cite-prefix">On 3/16/2026 5:46 PM, Pamela Chestek wrote:<=
/div>
<blockquote>
<p class=3D"ms-outlook-mobile-reference-message skipProofing">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 assum=
ing it hasn't be approved just because
 no one has asked for it before.</p>
<p class=3D"ms-outlook-mobile-reference-message skipProofing">Pam</p>
<div class=3D"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 href=3D"mailto:[email protected]" target=3D"_blank" rel=3D"nofollo=
w noopener noreferrer">[email protected]</a><br>
<a href=3D"http://www.chesteklegal.com/" target=3D"_blank" rel=3D"nofollow =
noopener noreferrer">www.chesteklegal.com</a><br>
<br>
<br>
</div>
<div class=3D"moz-cite-prefix">On 3/6/2026 5:47 AM, Max Mehl wrote:</div>
<blockquote>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr;font-family:'aptos' , 'arial' , 'helvetica' , sans-serif;font-s=
ize:12pt;color:rgb( 0 , 0 , 0 )">
Hi everyone,</div>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr;font-family:'aptos' , 'arial' , 'helvetica' , sans-serif;font-s=
ize:12pt;color:rgb( 0 , 0 , 0 )">
<br>
</div>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr;font-family:'aptos' , 'arial' , 'helvetica' , sans-serif;font-s=
ize: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=E2=80=99s realms, and request OSI=
=E2=80=99s approval of two licenses.</div>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr;font-family:'aptos' , 'arial' , 'helvetica' , sans-serif;font-s=
ize:12pt;color:rgb( 0 , 0 , 0 )">
<br>
</div>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr;font-family:'aptos' , 'arial' , 'helvetica' , sans-serif;font-s=
ize: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 =E2=80=9Cownerships=E2=80=9D of the project (CWI, CNRI=
, BeOpen, PSF).
<a href=3D"https://github.com/spdx/license-list-XML/issues/2197" target=3D"=
_blank" rel=3D"nofollow noopener noreferrer">
spdx/license-list-XML#2197</a>&nbsp;and an <a href=3D"https://lists.spdx.or=
g/g/Spdx-legal/topic/107252308" target=3D"_blank" rel=3D"nofollow noopener =
noreferrer">
email to spdx-legal@</a>&nbsp;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 class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr;font-family:'aptos' , 'arial' , 'helvetica' , sans-serif;font-s=
ize:12pt;color:rgb( 0 , 0 , 0 )">
<br>
</div>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr;font-family:'aptos' , 'arial' , 'helvetica' , sans-serif;font-s=
ize: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" target=3D"_blank" rel=3D"nofol=
low noopener noreferrer">
Python-2.0.1</a>. IIRC, the main difference between <a href=3D"https://spdx=
.org/licenses/Python-2.0.html" target=3D"_blank" rel=3D"nofollow noopener n=
oreferrer">
Python-2.0</a>&nbsp;and Python-2.0.1 is in the CNRI part, making it GPL com=
patible (the =E2=80=9CVirginia clause=E2=80=9D). SPDX lists this updated su=
b-part as
<a href=3D"https://spdx.org/licenses/CNRI-Python-GPL-Compatible.html" targe=
t=3D"_blank" rel=3D"nofollow noopener noreferrer">
CNRI-Python-GPL-Compatible</a>, a successor of <a href=3D"https://spdx.org/=
licenses/CNRI-Python.html" target=3D"_blank" rel=3D"nofollow noopener noref=
errer">
CNRI-Python</a>.</div>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr;font-family:'aptos' , 'arial' , 'helvetica' , sans-serif;font-s=
ize:12pt;color:rgb( 0 , 0 , 0 )">
<br>
</div>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr;font-family:'aptos' , 'arial' , 'helvetica' , sans-serif;font-s=
ize: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".&nbsp;</div>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr;font-family:'aptos' , 'arial' , 'helvetica' , sans-serif;font-s=
ize:12pt;color:rgb( 0 , 0 , 0 )">
<br>
</div>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr;font-family:'aptos' , 'arial' , 'helvetica' , sans-serif;font-s=
ize: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>&nbsp;and <b>CNRI-Python-GPL-Compatible</b>&nbsp;as Open=
 Source licenses, and mark Python-2.0 and CNRI-Python as superseded. Is the=
re any reason not to?</div>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr;font-family:'aptos' , 'arial' , 'helvetica' , sans-serif;font-s=
ize:12pt;color:rgb( 0 , 0 , 0 )">
<br>
</div>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr;font-family:'aptos' , 'arial' , 'helvetica' , sans-serif;font-s=
ize:12pt;color:rgb( 0 , 0 , 0 )">
Best,</div>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr;font-family:'aptos' , 'arial' , 'helvetica' , sans-serif;font-s=
ize:12pt;color:rgb( 0 , 0 , 0 )">
Max&nbsp;</div>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr;font-family:'aptos' , 'arial' , 'helvetica' , sans-serif;font-s=
ize:12pt;color:rgb( 0 , 0 , 0 )">
<br>
</div>
<div id=3D"ms-outlook-mobile-signature" style=3D"color:inherit;background-c=
olor:inherit">
<p class=3D"MsoNormal" style=3D"margin:0cm;font-family:'aptos' , sans-serif=
;font-size:11pt">
<span style=3D"color:black">--&nbsp;</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.com/=
mxmehl" style=3D"margin-top:0px;margin-bottom:0px" target=3D"_blank" rel=3D=
"nofollow noopener noreferrer">
cal.com/mxmehl</a></span><br data-mce-bogus=3D"1"></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>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr">
<br>
</div>
<hr>
<div class=3D"ms-outlook-mobile-reference-message skipProofing"><br>
<a href=3D"https://www.deutschebahn.com/pflichtangaben/20260305" target=3D"=
_blank" rel=3D"nofollow noopener noreferrer">Pflichtangaben anzeigen</a><br=
>
<br>
N=C3=A4here Informationen zur Datenverarbeitung im DB-Konzern finden Sie hi=
er: <a href=3D"https://www.deutschebahn.com/de/konzern/datenschutz" target=
=3D"_blank" rel=3D"nofollow noopener noreferrer">
https://www.deutschebahn.com/de/konzern/datenschutz</a><br data-mce-bogus=
=3D"1"></div>
<pre><div class=3D"moz-quote-pre">_________________________________________=
______
The opinions expressed in this email are those of the sender and not necess=
arily 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 href=3D"mailto:[email protected]" target=3D"_blank" r=
el=3D"nofollow noopener noreferrer">[email protected]</a=
>
<a href=3D"http://lists.opensource.org/mailman/listinfo/license-discuss_lis=
ts.opensource.org" target=3D"_blank" rel=3D"nofollow noopener noreferrer">h=
ttp://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensourc=
e.org</a>
</div></pre>
</blockquote>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di=
rection:ltr">
<br>
</div>
<pre><div class=3D"moz-quote-pre">_________________________________________=
______
The opinions expressed in this email are those of the sender and not necess=
arily 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 href=3D"mailto:[email protected]" target=3D"_blank" r=
el=3D"nofollow noopener noreferrer">[email protected]</a=
>
<a href=3D"http://lists.opensource.org/mailman/listinfo/license-discuss_lis=
ts.opensource.org" target=3D"_blank" rel=3D"nofollow noopener noreferrer">h=
ttp://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensourc=
e.org</a>
</div></pre>
</blockquote>
</div>
<br>
<hr>
<br>
<a href=3D"https://www.deutschebahn.com/pflichtangaben/20260319" target=3D"=
_blank" rel=3D"nofollow noopener noreferrer">Pflichtangaben anzeigen</a><br=
>
<br>
N=C3=A4here Informationen zur Datenverarbeitung im DB-Konzern finden Sie hi=
er: <a href=3D"https://www.deutschebahn.com/de/konzern/datenschutz" target=
=3D"_blank" rel=3D"nofollow noopener noreferrer">
https://www.deutschebahn.com/de/konzern/datenschutz</a>

<br>_______________________________________________<br>The opinions express=
ed in this email are those of the sender and not necessarily those of the O=
pen Source Initiative. Official statements by the Open Source Initiative wi=
ll be sent from an opensource.org email address.<br><br>License-discuss mai=
ling list<br>[email protected]<br>http://lists.opensourc=
e.org/mailman/listinfo/license-discuss_lists.opensource.org<br></blockquote=
></div></div></body></html>
--=_ace9577a-acb7-493c-80b9-59c8e8dcf695--


--===============6600522015036678159==
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=

--===============6600522015036678159==--