From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org, kevinb@redhat.com, tdevries@suse.de
Subject: Re: [PATCH v2] Require Python 3.4
Date: Fri, 30 May 2025 10:07:52 +0300 [thread overview]
Message-ID: <86tt52tw3b.fsf@gnu.org> (raw)
In-Reply-To: <20250529175552.1312658-1-tromey@adacore.com> (message from Tom Tromey on Thu, 29 May 2025 11:55:52 -0600)
> From: Tom Tromey <tromey@adacore.com>
> Cc: Tom Tromey <tromey@adacore.com>,
> Eli Zaretskii <eliz@gnu.org>,
> Kevin Buettner <kevinb@redhat.com>,
> Tom de Vries <tdevries@suse.de>
> Date: Thu, 29 May 2025 11:55:52 -0600
>
> I believe we previously agreed that the minimum supported Python
> version should be 3.4. This patch makes this change, harmonizing the
> documentation (which was inconsistent about the minimum version) and
> the code.
>
> New in v2: rebased, and removed a pre-3.4 workaround from __init__.py.
>
> Reviewed-By: Eli Zaretskii <eliz@gnu.org>
> Approved-by: Kevin Buettner <kevinb@redhat.com>
> Acked-By: Tom de Vries <tdevries@suse.de>
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31870
> ---
> gdb/NEWS | 2 ++
> gdb/README | 2 +-
> gdb/configure | 4 ++--
> gdb/configure.ac | 4 ++--
> gdb/doc/gdb.texinfo | 2 +-
> gdb/python/lib/gdb/__init__.py | 7 +------
> gdb/python/py-gdb-readline.c | 4 ----
> gdb/python/python-internal.h | 13 ++-----------
> 8 files changed, 11 insertions(+), 27 deletions(-)
Thanks, the documentation parts are okay.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
prev parent reply other threads:[~2025-05-30 7:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 17:55 Tom Tromey
2025-05-29 23:31 ` Kevin Buettner
2025-05-30 13:11 ` Tom Tromey
2025-07-25 9:33 ` Matthieu Longo
2025-07-25 9:38 ` Tom de Vries
2025-07-25 11:06 ` Eli Zaretskii
2025-05-30 7:07 ` Eli Zaretskii [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=86tt52tw3b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=tdevries@suse.de \
--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