Re: Time to drop plpython2?

From: Andres Freund <andres(at)anarazel(dot)de>
To: Joe Conway <mail(at)joeconway(dot)com>
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 19:37:16
Message-ID: 20220218193716.a7ds5c5ynazzt6dm@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2022-02-18 14:19:49 -0500, Joe Conway wrote:
> 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?

If python3 is in PATH, then you shouldn't need that part.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2022-02-18 19:46:39 Re: Time to drop plpython2?
Previous Message Joe Conway 2022-02-18 19:19:49 Re: Time to drop plpython2?