Re: Time to drop plpython2?
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org
Date: 2021-11-01T05:53:01Z
Lists: pgsql-hackers
On 31.10.21 19:45, Andres Freund wrote: > To me it seems time to drop plpython2 support. Supporting plpython2 > until ~7 years after python2 is EOL is already quite long... It'd be one > thing if it were completely painless, but imo it's not. > > I was about to list better plpython2/3 support (including the regex > replacements for the regress tests) as a TODO for the meson proposal, > but it doesn't really seem worth investing in that... Usually, we have dropped support for older Python versions when continued support would be a burden for some ongoing development project. This would certainly count as one of those, I think.
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