Re: Time to drop plpython2?

From: Joe Conway <mail(at)joeconway(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: Time to drop plpython2?
Date: 2022-02-18 20:35:37
Message-ID: e6575f7c-6e8c-1d9e-d961-8d5ebefe9cbb@joeconway.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/18/22 15:25, Andres Freund wrote:
> On 2022-02-18 14:46:39 -0500, Joe Conway wrote:
>> $ ll /usr/bin/python
>> lrwxrwxrwx. 1 root root 7 Mar 13 2021 /usr/bin/python -> python2
>> 8<-------------------
>
> Yea, that all looks fine. What's the problem if you don't specify the
> PYTHON=python3? We try python3, python in that order by default, so it should
> pick up the same python3 you specify explicitly?

Initially I just installed the python3 RPMs and when I tried running
manually it was still error'ing on configure due to finding python2.

Even after adding EXPORT PYTHON=python3 to my ~/.bash_profile I was
seeing the same.

By adding PYTHON => 'python3' to build-farm.conf I saw that the error
changed to indicate missing python3-devel package. Once I installed
that, everything went green.

Joe

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2022-02-18 20:41:30 Re: Removing more vacuumlazy.c special cases, relfrozenxid optimizations
Previous Message Andres Freund 2022-02-18 20:32:55 Re: Design of pg_stat_subscription_workers vs pgstats