public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: 洪伊 <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH] pl: fix can not build free-thread for plpython extension like 3.14t
Date: Thu, 15 Jan 2026 23:01:19 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAFDmy2xkZM5VOweB4Tjq_K2wgA7HN-Ok70f1aX_rCbhXHYp4vg@mail.gmail.com>
References: <CAFDmy2xkZM5VOweB4Tjq_K2wgA7HN-Ok70f1aX_rCbhXHYp4vg@mail.gmail.com>

=?UTF-8?B?5rSq5LyK?= <[email protected]> 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/[email protected]

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

view thread (4+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: [PATCH] pl: fix can not build free-thread for plpython extension like 3.14t
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox