From: Kevin Buettner <kevinb@redhat.com>
To: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>, legouguec@adacore.com
Subject: Re: [RFC] Bump minimum Python version to 3.4
Date: Fri, 2 Jun 2023 17:01:54 -0700 [thread overview]
Message-ID: <20230602170154.266355f1@f38-zws-nv> (raw)
In-Reply-To: <20230602163303.3945535-1-tromey@adacore.com>
On Fri, 2 Jun 2023 10:33:03 -0600
Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> wrote:
> 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.
I'm in favor of this change.
The patch LGTM also.
Kevin
next prev parent reply other threads:[~2023-06-03 0:01 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
2023-06-02 18:20 ` Paul Koning
2023-06-02 18:42 ` Eli Zaretskii
2023-06-03 0:01 ` Kevin Buettner [this message]
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=20230602170154.266355f1@f38-zws-nv \
--to=kevinb@redhat.com \
--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).