| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Renan Alves Fonseca <renanfonseca(at)gmail(dot)com>, Florents Tselai <florents(dot)tselai(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Devrim Gündüz <devrim(at)gunduz(dot)org>, Christoph Berg <myon(at)debian(dot)org> |
| Subject: | Re: What's our minimum supported Python version? |
| Date: | 2025-04-23 09:11:32 |
| Message-ID: | CAGECzQRo_GmHocSmq6cyZ=GNS4GvJbgT+Ag92hL+gGMT9iz0OQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 23 Apr 2025 at 00:33, Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> As long as the need to backport to PG18 doesn't freeze that
> conversation in place, I suppose.
I'm confused. Are you intending to backport new test infra to PG18?
Looking at the amount of python code that we currently have, I agree
with Tom: Making the few scripts that we have compatible with
Python3.6 seems the best solution for PG18. (especially since you
already have a patch that fixes the known issues).
Given the purpose and pretty small size of the scripts, I expect that
it'd be extremely rare for us to backport changes to them. e.g. I
doubt your oauth server would need many changes to keep working
correctly for the lifetime of PG18. Maybe it gets some minor fixes in
18.1 and/or 18.2 but other than that it seems really unlikely.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim Gündüz | 2025-04-23 09:13:38 | Re: What's our minimum supported Python version? |
| Previous Message | Jelte Fennema-Nio | 2025-04-23 09:03:46 | Re: What's our minimum supported Python version? |