Re: Python 2.5 vs the buildfarm

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
Subject: Re: Python 2.5 vs the buildfarm
Date: 2008-07-29 14:56:48
Message-ID: 10855.1217343408@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-07-29 15:08:13 Re: patch: Add a separate TRUNCATE permission
Previous Message Alvaro Herrera 2008-07-29 14:43:54 Re: pg_regress inputdir