Horton
Menu

Re: What's our minimum supported Python version?

Peter Eisentraut <peter@eisentraut.org>

View thread
From: Peter Eisentraut <peter@eisentraut.org>
To: Jacob Champion <jacob.champion@enterprisedb.com>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jelte Fennema-Nio <postgres@jeltef.nl>, Daniel Gustafsson <daniel@yesql.se>, pgsql-hackers@lists.postgresql.org, Devrim Gündüz <devrim@gunduz.org>
Date: 2025-04-29T06:30:33Z
Lists: pgsql-hackers 
On 24.04.25 18:20, Jacob Champion wrote:
> On Thu, Apr 24, 2025 at 7:59 AM Tom Lane <tgl@sss.pgh.pa.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.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. plpython: Remove obsolete test expected file

  2. Bump the minimum supported Python version to 3.6.8

  3. oauth: Support Python 3.6 in tests