[Python-Dev] Fixing 2.7.x
tismer at stackless.com
Mon Oct 6 21:18:23 CEST 2014
-----BEGIN PGP SIGNED MESSAGE-----
On 06.10.14 20:55, Zachary Ware wrote:
> On Mon, Oct 6, 2014 at 12:24 PM, Ned Deily <nad at acm.org> wrote:
>> 3. security: "fixing issues exploitable by attackers such as crashes,
>> privilege escalation and, optionally, other issues such as denial of
>> service attacks. Any other changes are not considered a security risk
>> and thus not backported to a security branch."
>> = 3.2.x and 3.3.x
> 3.1 is still in this category, is it not? According to PEP 375, it's
> a few months past due for its last release.
I don't think that the rules should be implicitly considered
compatible between the 2.X and 3.X series.
Python 2.X has a history that extends to X==6, X==5 and
even X==4, as a really conservative POV with an extent over more
than 10 years.
I believe, such a thing does not exist for the Python 3.X series
at all. My impression is that no 3.X user ever would want to stick
with any older version.
Is that true, or am I totally wrong?
cheers -- Chris
Christian Tismer :^) tismer at stackless.com
Software Consulting : http://www.stackless.com/
Karl-Liebknecht-Str. 121 : http://www.pydica.net/
14482 Potsdam : GPG key -> 0xFB7BEE0E
phone +49 173 24 18 776 fax +49 (30) 700143-0023
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org
-----END PGP SIGNATURE-----
More information about the Python-Dev