Re: Time to drop plpython2?

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Time to drop plpython2?
Дата
Msg-id 59eec9e5-f62a-4aeb-4cd6-ee5fddc2d6b4@enterprisedb.com
обсуждение исходный текст
Ответ на Re: Time to drop plpython2?  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Time to drop plpython2?  (Robert Haas <robertmhaas@gmail.com>)
Re: Time to drop plpython2?  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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 по дате отправления:

Предыдущее
От: Julien Rouhaud
Дата:
Сообщение: Re: Asynchronous and "direct" IO support for PostgreSQL.
Следующее
От: Masahiko Sawada
Дата:
Сообщение: Re: Add index scan progress to pg_stat_progress_vacuum