Re: Time to drop plpython2? - Mailing list pgsql-hackers

From Joe Conway
Subject Re: Time to drop plpython2?
Date
Msg-id e6575f7c-6e8c-1d9e-d961-8d5ebefe9cbb@joeconway.com
Whole thread Raw
In response to Re: Time to drop plpython2?  (Andres Freund <andres@anarazel.de>)
Responses Re: Time to drop plpython2?
List 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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Design of pg_stat_subscription_workers vs pgstats
Next
From: Peter Geoghegan
Date:
Subject: Re: Removing more vacuumlazy.c special cases, relfrozenxid optimizations