On Wed, Sep 8, 2010 at 6:55 PM, Paul Rubin wrote:
> Carl Banks writes:
>> Since Python 2.7 is released, Python 2.5 is no longer accepting bug
>> fixes, only security fixes. So be aware.
>
> Segfaults should be treated as security holes unless there's convincing
> reasons that no exploit is possi
In article ,
Thomas Jollans wrote:
>
>Also, Python 2.5 is frightfully old. [...]
"Frightfully"??? I'm sure plenty of people are still using Python 2.3
in production environments (certainly my last job did as of 1.5 years
ago, and I would be mildly surprised if they upgraded by now).
--
Aahz (
Carl Banks writes:
> Since Python 2.7 is released, Python 2.5 is no longer accepting bug
> fixes, only security fixes. So be aware.
Segfaults should be treated as security holes unless there's convincing
reasons that no exploit is possible. So the bug should be reported
against 2.5 as well as l
On Sep 8, 11:58 am, Kenneth Dombrowski wrote:
> Hi all,
>
> Before creating an issue @ bugs.python.org I wanted to run the
> following by everyone
>
> We are having a difficult time with what looks like a cPickle issue
> when given a data structure containing >15 nested dictionaries, but
> only wh
On Wednesday 08 September 2010, it occurred to Kenneth Dombrowski to exclaim:
> Environment is FreeBSD 8, Python 2.5.5
Which architecture?
Also, Python 2.5 is frightfully old. There's not really any problem with still
using it, but nobody's maintaining it upstream, so don't bother reporting a
b
