Peter Eisentraut <peter_e@gmx.net> writes:
> Am Tuesday, 29. July 2008 schrieb Greg Sabino Mullane:
>> What's not stable about having Python 2.5?
> I mean "stable" to mean "does not change (unnecessarily)".
I really don't understand Peter's objection here. This thread has
already consumed more person-time than I spent on applying the
back-patch. I note also that, in fact, the code that was wrong was
wrong according to pre-2.5 python as well. It accidentally failed
to fail on common architectures, but it was certainly doing things
that are undefined according to the C standard. So in my eyes this
was a bug fix.
regards, tom lane
