Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

Pavel Raiskup writes: > On Wednesday, April 25, 2018 12:17:05 AM CEST Peter Eisentraut wrote: >> On 4/24/18 07:13, Pavel Raiskup wrote: >>> What's the expected future migration path from plpython2 to plpython3 in >>> such cases? I'm thinking about rewrite of the docs and creating some >>> scripti

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

And Gentoo too. > PEP 394 points out that some distros (at least Arch) have already switched >

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

On 4/27/18 12:38, Pavel Raiskup wrote: > Well, also it depends what's meant by "get PEP 394 changed". My guess is > that distros might well avoid providing /bin/python if that PEP is > a concern.. that's actually typical situation in Fedora even now; python2 > package isn't installed by default.

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

On 2018-04-27 13:34:58 -0400, Tom Lane wrote: > Yeah, there's a separate set of questions about what happens during > pg_upgrade of a database containing the existing plpythonu extension. > > You could imagine hacking the dump/reload case by defining plpythonu > as an empty extension with a depend

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

Andres Freund writes: > 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

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

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

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

Pavel Raiskup writes: > On Friday, April 27, 2018 5:51:57 PM CEST Tom Lane wrote: >> We should evidently plan on making this stuff happen in v12, or we're >> going to be behind the curve. > Agreed, but I'm still not sure what would be the expected 2->3 migration > path. If that change happens in

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

On Friday, April 27, 2018 5:51:57 PM CEST Tom Lane wrote: > Note that there's a specific timeline there: they expect PEP 394 to get > changed not more than 2 years from now. I am not sure if Red Hat has > enough pull in the Python community to guarantee that will happen, but > do you want to bet a

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

Peter Eisentraut writes: > On 4/26/18 16:39, Tom Lane wrote: >> and I gather from Pavel's inquiry that the day >> is in sight when Fedora will do that. > According to the plan I found at > , they > will also wait for an update to PEP

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

Robert Haas writes: > Incidentally, it recently came to my notice that we're still issuing > hints that say: > Use CREATE LANGUAGE to load the language into the database. > That is now, and has been for some time, the wrong advice. We should > really be recommending CREATE EXTENSION. Right. It'

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

On 4/26/18 16:39, Tom Lane wrote: >> I don't think we should do that unless there is an update to PEP 394. > > PEP 394 points out that some distros (at least Arch) have already switched > "python" to mean "python3", My recollection is that PEP 394 was written because Arch jumped the gun and the P

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

On Thu, Apr 26, 2018 at 4:39 PM, Tom Lane wrote: > I'm not very sure how many moving parts would be involved in making that > happen. One thing we should probably do first is retire the pg_pltemplate > system catalog in favor of making PL extension scripts self-contained, > as you'd mentioned rec

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

Andrew Dunstan writes: > After installing python3, I switched buildfarm animal prion to build and > test with python3 instead of python2 a day or two ago. All this required > was setting PYTHON=/usr/bin/python3 in the environment. Everything else > Just Worked. That just means we've hacked the re

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

On 04/26/2018 04:39 PM, Tom Lane wrote: > Peter Eisentraut writes: >> On 4/25/18 04:50, Pavel Raiskup wrote: >>> So full drop is not what ask for now (it will be needed for lts/enterprise >>> distros for quite some time anyway), I just think that plpython3 should be >>> the default (by build sys

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

Peter Eisentraut writes: > On 4/25/18 04:50, Pavel Raiskup wrote: >> So full drop is not what ask for now (it will be needed for lts/enterprise >> distros for quite some time anyway), I just think that plpython3 should be >> the default (by build system, by 'plpythonu'=>'plpython3u', etc.). > I d

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

On 4/25/18 04:50, Pavel Raiskup wrote: > So full drop is not what ask for now (it will be needed for lts/enterprise > distros for quite some time anyway), I just think that plpython3 should be > the default (by build system, by 'plpythonu'=>'plpython3u', etc.). I don't think we should do that unle

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

Thanks Peter, On Wednesday, April 25, 2018 12:17:05 AM CEST Peter Eisentraut wrote: > On 4/24/18 07:13, Pavel Raiskup wrote: > > .. the status quo seems to be bit optimistic with the "distant future", > > and we should start thinking about dropping plpython2 support, same as > > upstream (a bit op

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

On 4/24/18 07:13, Pavel Raiskup wrote: > .. the status quo seems to be bit optimistic with the "distant future", > and we should start thinking about dropping plpython2 support, same as > upstream (a bit optimistically too, IMO) does [1]. I don't think we are going to drop Python 2 support anytime

obsoleting plpython2u and defaulting plpythonu to plpython3u

Forwarding to hackers. Hope that's OK after few days. Pavel -- Forwarded Message -- Subject: obsoleting plpython2u and defaulting plpythonu to plpython3u Date: Thursday, April 19, 2018, 11:56:40 AM CEST From: Pavel Raiskup To: pgsql-general Per current plpython