| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pavel Raiskup <praiskup(at)redhat(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: obsoleting plpython2u and defaulting plpythonu to plpython3u |
| Date: | 2018-04-27 17:28:20 |
| Message-ID: | 20180427172820.jpuvx3lnfgxvyvnx@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-04-27 17:34:58 | Re: obsoleting plpython2u and defaulting plpythonu to plpython3u |
| Previous Message | Tom Lane | 2018-04-27 17:19:43 | Re: obsoleting plpython2u and defaulting plpythonu to plpython3u |