Re: [PATCH] pl: fix can not build free-thread for plpython extension like 3.14t

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: 洪伊 <zouzou0208(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] pl: fix can not build free-thread for plpython extension like 3.14t
Date: 2026-01-16 04:01:19
Message-ID: 1010363.1768536079@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

=?UTF-8?B?5rSq5LyK?= <zouzou0208(at)gmail(dot)com> writes:
> This patch fix can not build plpython for free-thread python like
> python3.14t

We've gone to fairly considerable trouble to switch to using Python's
limited API, for reasons described here:

https://www.postgresql.org/message-id/ee410de1-1e0b-4770-b125-eeefd4726a24@eisentraut.org

I don't see why we should abandon that for the convenience of
somebody's evidently-nonstandard Python build.

The proposed patch also breaks the header isolation that
the separate plpython_system.h header is meant to maintain.
Arguably we should have #define'd Py_LIMITED_API inside
plpython_system.h, not where it is. But I don't feel a need
to mess with that without a far better argument for why
we should change this at all.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Tselebrovskiy 2026-01-16 04:22:10 Re: Proposal for enabling auto-vectorization for checksum calculations
Previous Message shveta malik 2026-01-16 03:46:55 Re: Simplify code building the LR conflict messages