From: Tom Lane <tgl@sss.pgh.pa.us>
To: =?UTF-8?B?5rSq5LyK?= <zouzou0208@gmail.com>
cc: pgsql-hackers@postgresql.org
Subject: Re: [PATCH] pl: fix can not build free-thread for plpython extension like 3.14t
In-reply-to: <CAFDmy2xkZM5VOweB4Tjq_K2wgA7HN-Ok70f1aX_rCbhXHYp4vg@mail.gmail.com>
References: <CAFDmy2xkZM5VOweB4Tjq_K2wgA7HN-Ok70f1aX_rCbhXHYp4vg@mail.gmail.com>
Comments: In-reply-to =?UTF-8?B?5rSq5LyK?= <zouzou0208@gmail.com>
	message dated "Fri, 16 Jan 2026 10:36:38 +0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1010362.1768536079.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 15 Jan 2026 23:01:19 -0500
Message-ID: <1010363.1768536079@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/1010363.1768536079%40sss.pgh.pa.us>
Precedence: bulk

=3D?UTF-8?B?5rSq5LyK?=3D <zouzou0208@gmail.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