| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Marco Atzeri <marco(dot)atzeri(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Resolving the python 2 -> python 3 mess |
| Date: | 2020-03-26 09:14:54 |
| Message-ID: | 94673ab9-dd0f-965a-3ca0-e2fe2e95c983@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-03-26 06:46, Marco Atzeri wrote:
> 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 ?
You have to configure and build the sources twice with different PYTHON
settings. It depends on your packaging system how to best arrange that.
> And how to build for multiples 3.x ?
That is not supported.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergei Kornilov | 2020-03-26 09:53:24 | Re: allow online change primary_conninfo |
| Previous Message | Laurenz Albe | 2020-03-26 09:12:39 | Re: Berserk Autovacuum (let's save next Mandrill) |