Re: What's our minimum supported Python version?
Jacob Champion <jacob.champion@enterprisedb.com>
From: Jacob Champion <jacob.champion@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Daniel Gustafsson <daniel@yesql.se>, pgsql-hackers@lists.postgresql.org
Date: 2025-04-22T16:23:25Z
Lists: pgsql-hackers
On Tue, Apr 22, 2025 at 9:04 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > I'm also not excited by the idea that an incidental > test script gets to dictate what the cutoff is. I agree, and I don't intend for the script to dictate that. > Maybe it's sufficient to make a documentation change here, and > say we support Python >= 3.5? I'd be okay with saying 3.6.8 > too, on the grounds that if anything older fails to work we'd > almost certainly just say "too bad". I'm definitely on board with pulling the minimum up, as high as we think we can get away with. If you're comfortable with 3.6(.8), I'd say let's start there. > But RHEL8 is widespread > enough that I think we need to keep making the effort for 3.6.8. Even if we can get side-by-side versions working? RHEL8 has a bunch of newer Python 3 versions available, according to the docs. And virtualenvs can do a lot of lifting for us in practice. Thanks, --Jacob
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
plpython: Remove obsolete test expected file
- 1a857348e47d 18.0 landed
-
Bump the minimum supported Python version to 3.6.8
- 45363fca6372 18.0 landed
-
oauth: Support Python 3.6 in tests
- 005ccae0f2d6 18.0 landed