Python 3.11 vs. Postgres

Started by Tom Laneover 4 years ago3 messageshackers

tgl@sss.pgh.pa.us

over 4 years ago

According to [1]https://bugzilla.redhat.com/show_bug.cgi?id=2023272, we need to stop including Python's <eval.h>.
I've not checked whether this creates any backwards-compatibility
issues.

regards, tom lane

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=2023272

Peter Eisentraut

peter_e@gmx.net

over 4 years ago

In reply to: Tom Lane (#1)

Re: Python 3.11 vs. Postgres

On 24.11.21 04:07, Tom Lane wrote:

According to [1], we need to stop including Python's <eval.h>.
I've not checked whether this creates any backwards-compatibility
issues.

regards, tom lane

[1] https://bugzilla.redhat.com/show_bug.cgi?id=2023272

See attached patch. The minimum Python version for this change is 2.4,
which is the oldest version supported by PG10, so we can backpatch this
to all live branches.

Tom Lane

tgl@sss.pgh.pa.us

over 4 years ago

In reply to: Peter Eisentraut (#2)

Re: Python 3.11 vs. Postgres

Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:

On 24.11.21 04:07, Tom Lane wrote:

According to [1], we need to stop including Python's <eval.h>.

See attached patch. The minimum Python version for this change is 2.4,
which is the oldest version supported by PG10, so we can backpatch this
to all live branches.

LGTM. Tested with v10 and prairiedog's Python 2.4.1.

regards, tom lane

Python 3.11 vs. Postgres

Attachments: