On 15.11.21 19:52, Peter Eisentraut wrote:
> I think we should just write to the build farm owners, we plan to drop
> python2 support in, say, 60 days, please update your setup to use
> python3 or disable python support.
This discussion stalled. I think we should do *something* for
PostgreSQL 15.
I suspect at this point, the Meson move isn't going to happen for
PostgreSQL 15. Even if the code were ready, which it is not, then this
kind of thing would surely be something more sensible to put into PG16
early rather than PG15 late. So I'm setting aside any concerns about
which Python 3.x is the appropriate minimum level.
There is the discussion [0], which involves raising the minimum Python
version from 2.6 to 2.7, which would affect some build farm members.
But if we're going to drop 2.x anyway for PG15, say, then we don't need
to spend time organizing a 2.6 to 2.7 transition. (Although
backpatching might be required.)
Also, I was recently doing some bug fixing work in PL/Python, and just
getting a Python 2 installation is not straightforward these days on the
sort of OS that might be on a development machine. So there is also
that driver for dropping Python 2.
I think what I wrote in the message I'm responding to is the best way
forward, although maybe with less than 60 days now.
Thoughts?
[0]:
https://www.postgresql.org/message-id/flat/c74add3c-09c4-a9dd-1a03-a846e5b2fc52%40enterprisedb.com