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

From Andres Freund
Subject Re: Time to drop plpython2?
Date
Msg-id 20220218202533.ekeeebfdmfdkut7x@alap3.anarazel.de
Whole thread Raw
In response to Re: Time to drop plpython2?  (Joe Conway <mail@joeconway.com>)
Responses Re: Time to drop plpython2?
List pgsql-hackers
Hi,

On 2022-02-18 14:46:39 -0500, Joe Conway wrote:
> On 2/18/22 14:37, Andres Freund wrote:
> > > That seems to have worked.
> > > 
> > > But the question is, is that the correct/recommended method?
> > 
> > If python3 is in PATH, then you shouldn't need that part.
> 
> Not quite -- python3 is definitely in the PATH:
> 
> 8<-------------------
> $ which python3
> /usr/bin/python3
> 8<-------------------
> 
> And I gather that merely installing python3 RPMs on a RHEL-esque 7.X system
> does not replace the python symlink:
> 
> 8<-------------------
> $ yum whatprovides /usr/bin/python
> 
> python-2.7.5-89.el7.x86_64 : An interpreted, interactive, object-oriented
> programming language
> Repo        : base
> Matched from:
> Filename    : /usr/bin/python
> 
> $ 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?

Or maybe I'm just misunderstanding what you're asking...

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: buildfarm warnings
Next
From: Andres Freund
Date:
Subject: Re: Design of pg_stat_subscription_workers vs pgstats