Horton

Re: Time to drop plpython2?

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
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: 2021-11-15T18:18:22Z
Lists: pgsql-hackers 
Andres Freund <andres@anarazel.de> writes:
> On 2021-11-15 12:19:51 -0500, Tom Lane wrote:
>> I was wondering about simply probing to see if python3 exists (and if
>> so, what version it is exactly), as an additional configure test that
>> doesn't hook into anything.  That would give us some information without
>> suddenly changing what is being tested.

> But this is probably a good compromise. Were you thinking of doing a proper
> autoconf test or just putting something like python3 --version || true in
> configure?

Hm, I had in mind an actual configure test; but since it's just a
temporary exploratory measure, shortcuts are fine.  However, I'm
not sure that what you suggest would result in capturing anything
in config.log.

> I guess it'd be easiest to interpret if we output the current PYTHON version
> and, iff < 3.0, also output the 'python3' version?

We'll already know if PYTHON is set, at least so far as the buildfarm
is concerned.

			regards, tom lane

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