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. And it can disappear entirely if
> that's too expensive for maintenance.

I'm wondering who this situation is going to be resolved. Is anyone
going to switch /usr/bin/python to Python 3 in the foreseeable future?
A few have tried and regretted it.

Or is /usr/bin/python just going to go away when Python 2 goes away?

What we do in PostgreSQL would IMO depend on which of these choices is
going to be the dominant one.

If the former, then we can just switch plpythonu around to be Python 3
(perhaps a configure option).

If the latter, then we don't need to do anything, except perhaps warn
people to upgrade.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services