Re: obsoleting plpython2u and defaulting plpythonu to plpython3u - Mailing list pgsql-hackers

From Andres Freund
Subject Re: obsoleting plpython2u and defaulting plpythonu to plpython3u
Date
Msg-id 20180427172820.jpuvx3lnfgxvyvnx@alap3.anarazel.de
Whole thread Raw
In response to Re: obsoleting plpython2u and defaulting plpythonu to plpython3u  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: obsoleting plpython2u and defaulting plpythonu to plpython3u  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2018-04-27 13:19:43 -0400, Tom Lane wrote:
> If we agree that something like this is the way to go, I wonder if we
> shouldn't squeeze it into v11.  If we wait till v12, that's not going
> to ship till late 2019, which is going to be getting uncomfortably
> close to when PEP 394 might change if we believe Fedora's schedule.

I think that'd be reasonable.

Another alternative would be to have a 'plpython' extension that depends
on plpython2. That'd require users to specify CASCADE when creating it,
but that actually seems like it could be a useful hint...  I think it's
probably not worth going that route though, because reassigning objects
from one extension to another is more work than reasonable...

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: obsoleting plpython2u and defaulting plpythonu to plpython3u
Next
From: Tom Lane
Date:
Subject: Re: obsoleting plpython2u and defaulting plpythonu to plpython3u