|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Andres Freund <andres(at)anarazel(dot)de>|
|Cc:||Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org|
|Subject:||Re: Time to drop plpython2?|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Andres Freund <andres(at)anarazel(dot)de> writes:
> On February 14, 2022 12:48:12 PM PST, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> We could I guess, but does it really buy anything? I'm sure that
>> some of the buildfarm still hasn't updated their Python installation,
>> but it'll be about the same failure we'd get from the final patch.
> I guess what I was actually wondering about - but didn't write - was whether it's worth rejecting python 2 with just configure / msvc perl changes initially.
Ah, I see. +1, that would let us start nagging the laggard buildfarm
owners right away. But I do think we want the rest of the cleanup
done pretty soon --- especially simplification of the plpython
regression test arrangements.
regards, tom lane
|Next Message||Tom Lane||2022-02-15 03:58:32||Re: Better error message for unsupported replication cases|
|Previous Message||Amit Kapila||2022-02-15 03:26:36||Re: Better error message for unsupported replication cases|