From: Kevin Buettner <kevinb@redhat.com>
To: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH] Make 'import gdb.events' work
Date: Fri, 15 Jul 2022 13:33:17 -0700 [thread overview]
Message-ID: <20220715133317.1bd0103b@f35-zws-1> (raw)
In-Reply-To: <20220607132025.2243948-1-tromey@adacore.com>
On Tue, 7 Jun 2022 07:20:25 -0600
Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> wrote:
> + /* Define all internal modules. These are all imported (and thus
> + created) during initialization. */
> + struct _inittab mods[3] =
> + {
> + { "_gdb", init__gdb_module },
> + { "_gdbevents", gdbpy_events_mod_func },
> + { nullptr, nullptr }
> + };
Something I just noticed while looking at a conflict while rebasing
my Python 3.11 deprecation patch:
Is there any reason not to do...
struct _inittab mods[] =
...
instead?
Since I've had to move this hunk of code, I've made the above tweak in
my (soon to come) v3 Python 3.11 deprecation patch.
Kevin
next prev parent reply other threads:[~2022-07-15 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 13:20 Tom Tromey
2022-07-05 16:35 ` Tom Tromey
2022-07-15 20:33 ` Kevin Buettner [this message]
2022-07-18 17:28 ` Tom Tromey
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=20220715133317.1bd0103b@f35-zws-1 \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).