From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v3 1/5] [gdb/python] Introduce py_{none, true, false, notimplemented} functions
Date: Fri, 15 May 2026 12:36:16 -0600 [thread overview]
Message-ID: <87zf20frkv.fsf@tromey.com> (raw)
In-Reply-To: <33140204-448e-4e6c-97e5-833b589f1732@suse.de> (Tom de Vries's message of "Fri, 15 May 2026 19:44:57 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> On 5/15/26 7:36 PM, Tom Tromey wrote:
Tom> + So for the limited C API 3.12 and newer, we could just return a
Tom> + "PyObject *" instead.
Tom> I think the sentence is correct, and I still don't understand why you
Tom> think its incorrect.
It's not incorrect about the implementation of Python, but it posits
that in some situation these functions could return a PyObject*.
However such a change would not be good. For one thing these things are
useful in places that operate generically on gdbpy_ref<>. But for
another, gdb should treat CPython as a black box to the degree possible
and not try to avoid inc/dec-refs on immortal objects. Whether an
object is immortal is for CPython to manage.
Tom
next prev parent reply other threads:[~2026-05-15 18:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 13:58 Tom de Vries
2026-05-15 13:58 ` [PATCH v3 2/5] [gdb/python] Remove Py_RETURN_{NONE, TRUE, FALSE, NOTIMPLEMENTED} Tom de Vries
2026-05-15 13:58 ` [PATCH v3 3/5] [gdb/python] Undefine " Tom de Vries
2026-05-15 14:05 ` Tom de Vries
2026-05-15 17:40 ` Tom Tromey
2026-05-15 13:58 ` [PATCH v3 4/5] [gdb/python] Use py_{none,false} more often Tom de Vries
2026-05-15 17:39 ` Tom Tromey
2026-05-15 13:58 ` [PATCH v3 5/5] [gdb/python] Use py_{none,notimplemented} " Tom de Vries
2026-05-15 17:38 ` Tom Tromey
2026-05-15 17:36 ` [PATCH v3 1/5] [gdb/python] Introduce py_{none, true, false, notimplemented} functions Tom Tromey
2026-05-15 17:44 ` Tom de Vries
2026-05-15 18:36 ` Tom Tromey [this message]
2026-05-15 19:08 ` Tom de Vries
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zf20frkv.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox