From: Tom de Vries <tdevries@suse.de>
To: Matthieu Longo <matthieu.longo@arm.com>,
Tom Tromey <tromey@adacore.com>,
Kevin Buettner <kevinb@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH v2] Require Python 3.4
Date: Fri, 25 Jul 2025 11:38:56 +0200 [thread overview]
Message-ID: <f8980832-5f11-4912-af0e-30c45eda3989@suse.de> (raw)
In-Reply-To: <14696e4d-3b6a-4538-ba21-d58ce7de02fc@arm.com>
On 7/25/25 11:33, Matthieu Longo wrote:
> On 2025-05-30 14:11, Tom Tromey wrote:
>>>>>>> "Kevin" == Kevin Buettner <kevinb@redhat.com> writes:
>>
>> Kevin> On Thu, 29 May 2025 11:55:52 -0600
>> Kevin> Tom Tromey <tromey@adacore.com> wrote:
>>
>>>> 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
>>
>> Kevin> LGTM, and it still has my approval.
>>
>> Thanks, I'm checking it in.
>>
>> Tom
>
> Hi,
>
> What is the reason for targeting Python 3.4 as the minimal supported
> version ?
> What is the distribution with such an old Python ?
>
See the PR.
Thanks,
- Tom
> Matthieu
next prev parent reply other threads:[~2025-07-25 9:39 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 [this message]
2025-07-25 11:06 ` Eli Zaretskii
2025-05-30 7:07 ` Eli Zaretskii
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=f8980832-5f11-4912-af0e-30c45eda3989@suse.de \
--to=tdevries@suse.de \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=matthieu.longo@arm.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