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: <20211104195443.dystyijvufveikcp@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>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Thu, 04 Nov 2021 12:54:43 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <350036.1636057599.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 04 Nov 2021 16:26:39 -0400
Message-ID: <350037.1636057599@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/350037.1636057599%40sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> Another thing I wondered about is what we want to do with the extension
> names. Do we want to leave it named plpython3u? Do we want to have a plp=
ython
> that depends on plpython3u?

I think we want to keep plpython3u.  Maybe we can point plpythonu
at that, but I'm concerned about the potential for user confusion.
In particular, I think there's a nonzero probability that someone
will choose to maintain plpython2u/plpythonu outside of core,
just because they still don't want to migrate their Python code.

> I'd be inclined to just keep it at plpython3u for now, but there's an ar=
gument
> that going for plpython would be better long term: Presumably there will=
 be
> python 4 at some point - but I'd expect that to not be a breaking releas=
e,
> given the disaster that python 3 is. Making a non-versioned name better?

Meh.  If there is a python 4, I'd expect it to be named that way precisely
because it *is* a breaking release.  Why would we set ourselves up for
a repeat of this mess?

			regards, tom lane