From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
cc: Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org
Subject: Re: Time to drop plpython2?
In-reply-to: <85eb62cd-76f3-d01f-79ef-144173c16edc@enterprisedb.com>
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>
Comments: In-reply-to Peter Eisentraut <peter.eisentraut@enterprisedb.com>
	message dated "Wed, 10 Nov 2021 11:56:10 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2057148.1636943071.1@sss.pgh.pa.us>
Date: Sun, 14 Nov 2021 21:24:31 -0500
Message-ID: <2057149.1636943071@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2057149.1636943071%40sss.pgh.pa.us>
Precedence: bulk

... btw, there's a fairly critical gating factor for any plan to drop
python2 support: the buildfarm.  I just counted, and there are exactly
as many members running python 2.x as 3.x (49 apiece), not counting
Windows machines that aren't running configure.  We can't commit
something that's going to make half the buildfarm go red.

(It's likely that some fraction of them do already have python3 installed,
in which case the search order change Peter recommended would be enough to
fix it.  But I'm sure not all do.)

This ties into the business about converting the build system to meson,
as that also requires python 3 --- with, IIUC, a higher minimum version
than we might otherwise need.  I'm disinclined to cause two separate
flag days for buildfarm owners, so what I now think is we ought to put
this idea on the shelf until we've finished that conversion or decided
we're not gonna do it.  We need to identify exactly what needs to be
installed before we start pestering the owners.

			regards, tom lane