From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org, legouguec@adacore.com
Subject: Re: [RFC] Bump minimum Python version to 3.4
Date: Fri, 02 Jun 2023 21:14:50 +0300 [thread overview]
Message-ID: <83r0qtafz9.fsf@gnu.org> (raw)
In-Reply-To: <20230602163303.3945535-1-tromey@adacore.com> (message from Tom Tromey via Gdb-patches on Fri, 2 Jun 2023 10:33:03 -0600)
> Cc: legouguec@adacore.com,
> Tom Tromey <tromey@adacore.com>
> Date: Fri, 2 Jun 2023 10:33:03 -0600
> From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
>
> While looking into the f-string issue, I noticed that the README
> documents 3.2 as the minimum Python version, while gdb.texinfo says
> 3.0.2. Asking on irc, I found out that SuSE's "LTS" ships 3.4, and
> RHEL 7 ships 3.6. Based on this I think it's reasonable to bump the
> minimum required version to 3.4.
> ---
> gdb/NEWS | 2 ++
> gdb/README | 2 +-
> gdb/doc/gdb.texinfo | 2 +-
> gdb/python/py-gdb-readline.c | 4 ----
> gdb/python/python-internal.h | 11 -----------
> 5 files changed, 4 insertions(+), 17 deletions(-)
If the increase in the minimum supported versions is agreed upon, the
documentation parts of this are OK.
Thanks.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2023-06-02 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 16:33 Tom Tromey
2023-06-02 18:01 ` Simon Marchi
2023-06-02 18:14 ` Eli Zaretskii [this message]
2023-06-02 18:20 ` Paul Koning
2023-06-02 18:42 ` Eli Zaretskii
2023-06-03 0:01 ` Kevin Buettner
2023-06-07 9:41 ` Andrew Burgess
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=83r0qtafz9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=legouguec@adacore.com \
--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).