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

From Tom Lane
Subject Re: obsoleting plpython2u and defaulting plpythonu to plpython3u
Date
Msg-id 7702.1524782510@sss.pgh.pa.us
Whole thread Raw
In response to Re: obsoleting plpython2u and defaulting plpythonu to plpython3u  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List pgsql-hackers
Andrew Dunstan <andrew.dunstan@2ndquadrant.com> 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 regression tests to the point where
they work in that environment ;-).  An installation from that code
would still think plpythonu means plpython2u.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Is there a memory leak in commit 8561e48?
Next
From: Michael Paquier
Date:
Subject: Re: Is there a memory leak in commit 8561e48?