[Python-Dev] License() release list is imcomplete; intentional?

MRAB python at mrabarnett.plus.com
Tue Sep 17 17:48:44 CEST 2013


On 17/09/2013 16:37, Terry Reedy wrote:
> On 2.7, >>> license() return a text that includes a complete list of
> releases from 1.6 to 2.7 and stops there
>       Release         Derived     Year        Owner       GPL-
>                       from                                compatible? (1)
>
>       0.9.0 thru 1.2              1991-1995   CWI         yes
>       1.3 thru 1.5.2  1.2         1995-1999   CNRI        yes
>       1.6             1.5.2       2000        CNRI        no
>       2.0             1.6         2000        BeOpen.com  no
> ...
>       2.6.5           2.6.4       2010        PSF         yes
>       2.7             2.6         2010        PSF         yes
>
> Was it intentional to stop with 2.7 and not continue with 2.7.1, etc?
>
> On 3.3.2, the 2.x list ends with 2.6.5 and never mentions 2.7. Intentional?
> It then jumps back to 3.0 and ends with the 'previous' release, 3.3.1.
> Should 3.3.2 be included in the 3.3.2 list?
>
> ...
>       2.6.4           2.6.3       2009        PSF         yes
>       2.6.5           2.6.4       2010        PSF         yes
>       3.0             2.6         2008        PSF         yes
>       3.0.1           3.0         2009        PSF         yes
> ...
>       3.2.4           3.2.3       2013        PSF         yes
>       3.3.0           3.2         2012        PSF         yes
>       3.3.1           3.3.0       2013        PSF         yes
>
To me it looks like Python 2.7 isn't mentioned in the licence for
Python 3 because Python 3 is derived from Python 2.6 and Python 2.7 is
on a different branch, so it isn't relevant.


More information about the Python-Dev mailing list