Re: What's our minimum supported Python version?

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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-29 06:30:33
Message-ID: 94aaa086-0b55-49d6-a411-48761099feaf@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 24.04.25 18:20, Jacob Champion wrote:
> 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...)

I like the change to "supported", that's useful.

I would just write 3.6 instead of 3.6.8. We've never tracked the third
version component for Python.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2025-04-29 06:36:48 Re: allow changing autovacuum_max_workers without restarting
Previous Message Amit Kapila 2025-04-29 05:45:24 Re: DOCS - create publication (tweak for generated columns)