Horton

Re: Time to drop plpython2?

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org
Date: 2021-11-15T22:45:52Z
Lists: pgsql-hackers 
On 15.11.21 20:26, Tom Lane wrote:
> * Our docs claim the minimum 3.x version for pl/python itself is 3.1,
> but this is unbacked by any testing; the oldest 3.x in the buildfarm
> is 3.4.3 (three such animals).

I confirmed locally that 3.2.6 still works with PL/Python.  I expect 
that Python 3.1 also still works, except that I can't build it at the 
moment.  Python 3.0.* was sort of a dud, so it's not really interesting 
to consider.

Partially because of the need to keep supporting Python 2, there hasn't 
been any work done in PL/Python to make use of any newer APIs, so the 
Python 3 minimum version is frozen in time at the moment.

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