Re: Time to drop plpython2?
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
pgsql-hackers@postgresql.org
Date: 2022-02-14T20:48:12Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > On 2022-02-14 14:18:58 -0500, Tom Lane wrote: >> Well, it's mid-February. Do we have a python2-removal patch >> that's ready to go? > I can refresh mine. Iit might be good to first reapply > f201da39edc - "Make configure prefer python3 to plain python." > for a few days? 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. regards, tom lane
Commits
-
plpython: add missing plpython.h include to plpy_plpymodule.h
- 54c72eb5e5e6 15.0 landed
-
plpython: Adjust docs after removal of Python 2 support.
- 4228cabb72bb 15.0 landed
-
plpython: Code cleanup related to removal of Python 2 support.
- 9b7e24a2cb37 15.0 landed
-
plpython: Remove regression test infrastructure for Python 2.
- db23464715f4 15.0 landed
-
plpython: Remove plpythonu, plpython2u and associated transform extensions.
- 76a29adee749 15.0 landed
-
plpython: Reject Python 2 during build configuration.
- 19252e8ec938 15.0 landed
-
Add traceback information to PL/Python errors
- 2bd78eb8d51c 9.1.0 cited