Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Koning via Gdb-patches <gdb-patches@sourceware.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tromey@adacore.com>,
	gdb-patches@sourceware.org, legouguec@adacore.com
Subject: Re: [RFC] Bump minimum Python version to 3.4
Date: Fri, 2 Jun 2023 14:20:29 -0400	[thread overview]
Message-ID: <39E6ADFC-2253-4391-89BA-3CDC682677BE@comcast.net> (raw)
In-Reply-To: <83r0qtafz9.fsf@gnu.org>



> On Jun 2, 2023, at 2:14 PM, Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org> wrote:
> 
>> 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.

Given that python.org tells us the oldest supported version is 3.6, and that one goes off support at the end of this month, it might make sense to raise the minimum to 3.6 or 3.7.

	paul


  reply	other threads:[~2023-06-02 18:20 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
2023-06-02 18:14 ` Eli Zaretskii via Gdb-patches
2023-06-02 18:20   ` Paul Koning via Gdb-patches [this message]
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=39E6ADFC-2253-4391-89BA-3CDC682677BE@comcast.net \
    --to=gdb-patches@sourceware.org \
    --cc=eliz@gnu.org \
    --cc=legouguec@adacore.com \
    --cc=paulkoning@comcast.net \
    --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