Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Pavel Raiskup <praiskup(at)redhat(dot)com>, PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: obsoleting plpython2u and defaulting plpythonu to plpython3u
Date: 2018-04-26 22:41:50
Message-ID: 7702.1524782510@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-04-27 00:13:22 Re: Is there a memory leak in commit 8561e48?
Previous Message Tom Lane 2018-04-26 22:36:01 Re: Is there a memory leak in commit 8561e48?