I wrote:
> Christoph Berg writes:
>> As python2 is EOL very soon, I'd say that point is now, i.e. we should
>> make plpythonu.control point at plpython3u in PG13+.
> We're starting to work on that; it's not a trivial change. Among other
> things, pg_pltemplate has got pointers at plpython2 as we
On Thu, Nov 7, 2019 at 6:04 PM Christoph Berg wrote:
> How do other packagers handle that? Are you still supporting python2?
> Would it be ok to make plpythonu.control point at python3 in PG12 in
> Debian, even the upstream default is still python2?
Speaking for Fedora and RHEL, I'd say the best w
Re: Tom Lane 2019-11-07 <14186.1573147...@sss.pgh.pa.us>
> > And probably drop python2 support altogether.
>
> I think it'll be quite some time before that happens. People who
> are still using ancient versions of Postgres are not likely to be
> impressed by arguments about how python2 is out of
Christoph Berg writes:
> The docs currently say
> The language named plpythonu implements
> PL/Python based on the default Python language variant, which is
> currently Python 2. (This default is independent of what any
> local Python installations might consider to be
>
