public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Robert Haas <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: Time to drop plpython2?
Date: Mon, 15 Nov 2021 16:12:12 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+TgmobvHf81EsX8x5aNw-N-3vOvM7bJNhPW1ZMDhuGsfoZAxA@mail.gmail.com>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CA+TgmobvHf81EsX8x5aNw-N-3vOvM7bJNhPW1ZMDhuGsfoZAxA@mail.gmail.com>

Robert Haas <[email protected]> writes:
> On Mon, Nov 15, 2021 at 3:30 PM Tom Lane <[email protected]> wrote:
>> The info I checked said that RHEL7 originally shipped with 3.3.

> It'd only be an issue if they want to compile from source, right?
> We're not speaking of changing the runtime prerequisites, IIUC.

I'm not sure.  Does it make sense to document that pl/python has
a different Python version requirement than the build system does?
If we do, who exactly is going to be testing that such a combination
works?  Will it even be possible to compile pl/python against Python
headers/libs of a different Python generation than meson is running
under?

ISTM we'd be a lot better off saying "the minimum Python version is
3.something", full stop, and then making sure that that minimum is
represented in the buildfarm.  But it's not quite clear yet what
"something" needs to be.

> I think it's really important that we continue to run on all of the
> supported Linux distributions and even some recently-out-of-support
> ones if they are popular.

I agree completely, which is why I'm raising the point.

			regards, tom lane

view thread (26+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Time to drop plpython2?
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox