From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
        pgsql-hackers@postgresql.org
Subject: Re: Time to drop plpython2?
In-reply-to: <20211115170632.buql3valv5mlnbni@alap3.anarazel.de>
References: <20211031184548.g4sxfe47n2kyi55r@alap3.anarazel.de>
 <08a65981-7fec-1b9b-4061-6e3086c05914@enterprisedb.com>
 <3fc1211d-960b-4b2f-3e96-a6099db847fc@enterprisedb.com>
 <20211104195443.dystyijvufveikcp@alap3.anarazel.de>
 <85eb62cd-76f3-d01f-79ef-144173c16edc@enterprisedb.com>
 <2057149.1636943071@sss.pgh.pa.us>
 <20211115170632.buql3valv5mlnbni@alap3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Mon, 15 Nov 2021 09:06:32 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2138216.1636996791.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 15 Nov 2021 12:19:51 -0500
Message-ID: <2138217.1636996791@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2138217.1636996791%40sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> On 2021-11-14 21:24:31 -0500, Tom Lane wrote:
>> (It's likely that some fraction of them do already have python3 install=
ed,
>> in which case the search order change Peter recommended would be enough=
 to
>> fix it.  But I'm sure not all do.)

> How about committing the order change alone? That seems like something
> warranted completely in isolation? Afterwards we can see how many run wh=
at and
> go from there?

I don't think that's warranted.  The existing design is that we let
the user say which python is "python", and I do not think we should
change that in advance of actually dropping python2 support.

I was wondering about simply probing to see if python3 exists (and if
so, what version it is exactly), as an additional configure test that
doesn't hook into anything.  That would give us some information without
suddenly changing what is being tested.

			regards, tom lane