Re: Time to drop plpython2? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Time to drop plpython2?
Date
Msg-id 59eec9e5-f62a-4aeb-4cd6-ee5fddc2d6b4@enterprisedb.com
Whole thread Raw
In response to Re: Time to drop plpython2?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Time to drop plpython2?
Re: Time to drop plpython2?
List pgsql-hackers
On 11.01.22 17:06, Tom Lane wrote:
> Nonetheless, we need to make a recommendation to the
> buildfarm owners about what's the minimum python3 version we intend
> to support going forward.  Do we want to just set it at 3.6, with
> the expectation that the meson move will happen before too long?

Well, the minimum supported version has always been the oldest version 
that actually works.  I don't think we ever said, we support >= X, even 
though < X still actually works, about any dependency.

I don't care much to tie this to Meson right now.  Meson might well move 
to 3.8 next week and ruin this whole scheme.

I'm okay with issuing some sort of recommendation for what is reasonable 
to test, and 3.5 or 3.6 seems like a good cutoff, considering what LTS 
OS currently ship.  But I'm not sure if that is the same as "support".




pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: Asynchronous and "direct" IO support for PostgreSQL.
Next
From: Masahiko Sawada
Date:
Subject: Re: Add index scan progress to pg_stat_progress_vacuum