Re: Resolving the python 2 -> python 3 mess

From: Marco Atzeri <marco(dot)atzeri(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Resolving the python 2 -> python 3 mess
Date: 2020-03-26 05:46:05
Message-ID: 1a7741fa-6064-8800-45dd-0f8bbf8d9f7f@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Am 17.02.2020 um 17:49 schrieb Tom Lane:
> We've had multiple previous discussions of $SUBJECT (eg [1][2]),
> without any resolution of what to do exactly. Thinking about this
> some more, I had an idea that I don't think has been discussed.
> To wit:
>
> 1. On platforms where Python 2.x is still supported, recommend that
> packagers continue to build both plpython2 and plpython3, same as now.
>

there is some documentation on how to build both ?
The INSTALL gives no hint.

And how to build for multiples 3.x ?

Currently for Cygwin package I am building only 2.x and it is clearly
not a good situation.

Regards
Marco

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-03-26 06:22:06 Re: allow online change primary_conninfo
Previous Message Michael Paquier 2020-03-26 05:39:59 Re: pgbench - add \aset to store results of a combined query