RetroSearch Browse

Tue Oct 7 01:13:29 CEST 2014 · https://mail.python.org/pipermail/python-dev/2014-October/136579.html

In article 
<CAKJDb-P6nx5szhBeuxv0fWSJ+-5=U1cD6aY--eD2YqeWwRK4-g at mail.gmail.com>,
 Zachary Ware <zachary.ware+pydev at gmail.com> 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.
> http://legacy.python.org/dev/peps/pep-0375/#maintenance-releases

I don't think Benjamin was planning any further security releases.  But, 
in any case, the PEP should be updated, I guess.  Benjamin?

-- 
 Ned Deily,
 nad at acm.org

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2014-October/136579.html below:

[Python-Dev] Fixing 2.7.x