Horton

Re: Time to drop plpython2?

Joe Conway <mail@joeconway.com>

View thread View on postgr.es
From: Joe Conway <mail@joeconway.com>
To: Andres Freund <andres@anarazel.de>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org, Andrew Dunstan <andrew@dunslane.net>
Date: 2022-02-18T19:19:49Z
Lists: pgsql-hackers 
On 2/17/22 13:08, Andres Freund wrote:
> On 2022-02-16 23:14:46 -0800, Andres Freund wrote:
>> > Done. Curious how red the BF will turn out to be. Let's hope it's not
>> > too bad.

>> - rhinoceros
> 
> Joe replied that he is afk, looking into it tomorrow.

I installed python3 packages (initially forgetting the devel package -- 
d'oh!) and changed build-farm.conf thusly:

8<-------------------
***************
*** 185,190 ****
--- 185,193 ----

         build_env => {

+               # specify python 3
+               PYTHON => 'python3',
+
                 # use a dedicated cache for the build farm. this should 
give us
                 # very high hit rates and slightly faster cache searching.
                 #
8<-------------------

That seems to have worked.

But the question is, is that the correct/recommended method?

Joe
-- 
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development

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