From: Tom Tromey <tom@tromey.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: k4lizen <k4lizen@proton.me>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/docs] use a clearer example for gdb lexing
Date: Wed, 30 Sep 2026 08:09:43 -0600 [thread overview]
Message-ID: <871paaj0ew.fsf@tromey.com> (raw)
In-Reply-To: <86qzic1v13.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 29 Sep 2026 08:33:28 +0300")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Mon, 28 Sep 2026 23:21:40 +0000
>> From: k4lizen <k4lizen@proton.me>
>>
>> The old one raised a SyntaxWarning, and this one
>> allows the reader to focus on the GDB lexing
>> without having to think about what python is
>> doing.
Eli> Thanks. Is the new variant you suggest supported by all the versions
Eli> of Python we currently support?
Yeah. But also IMO it doesn't matter, Python developers generally
update and it's gdb that is weird in using obsolete versions.
Eli> Also, I think this should be reviewed by someone who knows Python
Eli> better than I do (which is close to nothing), because this is not just
Eli> a documentation issue.
It's fine, I'm going to check it in momentarily.
Tom
prev parent reply other threads:[~2026-09-30 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 23:21 k4lizen
2026-09-29 5:33 ` Eli Zaretskii
2026-09-30 14:09 ` Tom Tromey [this message]
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=871paaj0ew.fsf@tromey.com \
--to=tom@tromey.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=k4lizen@proton.me \
/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