Re: Time to drop plpython2?

Andres Freund <andres@anarazel.de>

From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>, pgsql-hackers@postgresql.org
Date: 2022-02-15T06:01:31Z
Lists: pgsql-hackers

Attachments

Hi,

On 2022-02-14 22:57:37 -0500, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > On February 14, 2022 12:48:12 PM PST, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> We could I guess, but does it really buy anything?  I'm sure that
> >> some of the buildfarm still hasn't updated their Python installation,
> >> but it'll be about the same failure we'd get from the final patch.
> 
> > I guess what I was actually wondering about - but didn't write - was whether it's worth rejecting python 2 with just  configure / msvc perl changes initially.
> 
> Ah, I see.  +1, that would let us start nagging the laggard buildfarm
> owners right away.

Cool.


> But I do think we want the rest of the cleanup done pretty soon ---
> especially simplification of the plpython regression test arrangements.

That part I have mostly ready (worked as part of a rebase of the meson tree
sometime last weekend). It's trawling through the docs, the msvc build scripts
and some plpython C code that's a bit more work...

Attached the state as I have in the meson tree. Will split out the configure
test tomorrow. Might or might get through the msvc scripts and docs as well.

Greetings,

Andres Freund

Commits

  1. plpython: add missing plpython.h include to plpy_plpymodule.h

  2. plpython: Adjust docs after removal of Python 2 support.

  3. plpython: Code cleanup related to removal of Python 2 support.

  4. plpython: Remove regression test infrastructure for Python 2.

  5. plpython: Remove plpythonu, plpython2u and associated transform extensions.

  6. plpython: Reject Python 2 during build configuration.

  7. Add traceback information to PL/Python errors