[License-review] Python licenses: Python-2.0.1, PSF-2.0, CNRI-Python-GPL-Compatible

McCoy Smith mccoy at lexpan.law
Fri Aug 28 02:55:27 UTC 2026


On 8/27/2026 7:33 PM, Richard Fontana via License-review wrote:
> On Thu, Aug 27, 2026 at 3:13 PM McCoy Smith <mccoy at lexpan.law> wrote:
>
>> So I don't think anything needs to be submitted or done yet although the
>> statement "Important that PSF-2.0 will also be included in the review as
>> it is used stand-alone and is also part of Python-2.0.1" is inconsistent
>> with the proposal to approve Python-2.0.1 and supersede Python-2.0 aka
>> PSF-2.0.
> I might be misunderstanding something you're saying, but to be clear
> Python-2.0 and PSF-2.0 are not the same license. Python-2.0 is the
> seemingly erroneous version of the CPython "stack license", while
> PSF-2.0 is the license at the top of the Python-2.0 (and Python-2.0.1)
> stacks.
OSI was asked to approve the Python-2.0.1 license and it was proposed to 
"mark Python-2.0 as either Superseded or Voluntarily Retired" if it was 
approved. That's what the Board voted to do. If someone is saying that 
that was not the desired course of action, even though the e-mail 
proposing this was supposedly done in coordination with the Python 
Software Foundation, I'd like to hear from the PSF that that was not the 
desired result and what they'd like done instead. If it is to Retire 
"Python-2.0" (the one currently showing as approved by OSI 
https://opensource.org/license/Python-2.0) and approve "PSF-2.0," then a 
request on license-discuss ought to be made to do that. And I'd also 
like it if that submission be made by someone who has confirmed with PSF 
that that's what they want (which was done with the submissions of 
Python-2.0.1 and CNRI-Python-GPL-Compatible.


More information about the License-review mailing list