From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Cc: legouguec@adacore.com
Subject: Re: [RFC] Bump minimum Python version to 3.4
Date: Fri, 2 Jun 2023 14:01:30 -0400 [thread overview]
Message-ID: <9ae8d6c1-d5b6-ba58-5489-0a721807899d@simark.ca> (raw)
In-Reply-To: <20230602163303.3945535-1-tromey@adacore.com>
On 6/2/23 12:33, Tom Tromey via Gdb-patches 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.
This is fine with me, but for reference here's the previous attempt at
doing this:
https://inbox.sourceware.org/gdb-patches/20220107152921.2858909-3-simon.marchi@polymtl.ca/#r
Simon
next prev parent reply other threads:[~2023-06-02 18:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 16:33 Tom Tromey via Gdb-patches
2023-06-02 18:01 ` Simon Marchi via Gdb-patches [this message]
2023-06-02 18:14 ` Eli Zaretskii via Gdb-patches
2023-06-02 18:20 ` Paul Koning via Gdb-patches
2023-06-02 18:42 ` Eli Zaretskii via Gdb-patches
2023-06-03 0:01 ` Kevin Buettner via Gdb-patches
2023-06-07 9:41 ` Andrew Burgess via Gdb-patches
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=9ae8d6c1-d5b6-ba58-5489-0a721807899d@simark.ca \
--to=gdb-patches@sourceware.org \
--cc=legouguec@adacore.com \
--cc=simark@simark.ca \
--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