Horton

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Pavel Raiskup <praiskup@redhat.com>, PostgreSQL Hacker <pgsql-hackers@postgresql.org>
Date: 2018-04-26T22:41:50Z
Lists: 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

Commits

  1. Adjust hints and docs to suggest CREATE EXTENSION not CREATE LANGUAGE.