| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, 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 15:16:59 |
| Message-ID: | 1029706.1745939819@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
> On 24.04.25 18:20, Jacob Champion wrote:
>> 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.
On the reading that "supported" means "we'll try to fix a problem
rather than telling you to use a newer Python", I suspect that the
correct thing to say is 3.6.8 not 3.6. There may be no difference
in practice; but if push comes to shove I don't think we'd support
a 3.6.x Python version that appears in no LTS distro.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2025-04-29 15:27:05 | Re: libpq: Add PQapplicationname() function |
| Previous Message | Japin Li | 2025-04-29 15:13:35 | Re: libpq: Add PQapplicationname() function |