Re: What's our minimum supported Python version?

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Devrim Gündüz <devrim(at)gunduz(dot)org>
Subject: Re: What's our minimum supported Python version?
Date: 2025-04-24 16:20:44
Message-ID: CAOYmi+=94HOyd-jnMYwsnH+9ATv=5YHYmC3kw_xgLXYhmyCvGA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 24, 2025 at 7:59 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I'm still content with the idea of deciding that 3.6 is now our
> cutoff.

Seems like no one is pushing hard for an earlier version, yet, so
here's a patch with your suggested wording from upthread. I'm not sure
if this meets Peter's request for precision. (Though I'm not really
excited about documenting more precision than we are testing for...)

> If someone comes along and complains because
> oauth_server.py doesn't work on an older version, it's up to them
> to provide a patch.

As an aside, EL7's standard libcurl is too old to pass our current
configure checks, so I think someone would really have to go out of
their way to get to that point.

--Jacob

Attachment Content-Type Size
0001-Bump-the-minimum-supported-Python-version-to-3.6.8.patch application/octet-stream 1.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Borodin 2025-04-24 16:32:44 Re: [PATCH] dynahash: add memory allocation failure check
Previous Message David Steele 2025-04-24 15:34:29 Re: Improve verification of recovery_target_timeline GUC.