From: | Christoph Berg <myon(at)debian(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL Packagers <pgsql-packagers(at)postgresql(dot)org>, git(at)rmr(dot)ninja |
Subject: | Re: plpythonu -> python3 |
Date: | 2019-11-07 17:38:53 |
Message-ID: | 20191107173853.GB27040@msg.df7cb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Re: Tom Lane 2019-11-07 <14186(dot)1573147925(at)sss(dot)pgh(dot)pa(dot)us>
> > And probably drop python2 support altogether.
>
> I think it'll be quite some time before that happens. People who
> are still using ancient versions of Postgres are not likely to be
> impressed by arguments about how python2 is out of support.
Fwiw, I meant to suggest dropping python2 support in PG13+. (At the
moment there are some "interesting" scripts in src/pl/plpython that
convert the plpython2 things on the fly to be python3 compatible,
these could go away, simplifying some parts of the build system.)
Christoph
From | Date | Subject | |
---|---|---|---|
Next Message | Patrik Novotny | 2019-11-07 17:56:34 | Re: plpythonu -> python3 |
Previous Message | Alvaro Herrera | 2019-11-07 17:38:29 | Re: Checking return value of SPI_execute |