public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Koning <paulkoning@comcast.net>
Cc: tromey@adacore.com, gdb-patches@sourceware.org, legouguec@adacore.com
Subject: Re: [RFC] Bump minimum Python version to 3.4
Date: Fri, 02 Jun 2023 21:42:43 +0300	[thread overview]
Message-ID: <83o7lxaeos.fsf@gnu.org> (raw)
In-Reply-To: <39E6ADFC-2253-4391-89BA-3CDC682677BE@comcast.net> (message from Paul Koning on Fri, 2 Jun 2023 14:20:29 -0400)

> From: Paul Koning <paulkoning@comcast.net>
> Date: Fri, 2 Jun 2023 14:20:29 -0400
> Cc: Tom Tromey <tromey@adacore.com>,
>  gdb-patches@sourceware.org,
>  legouguec@adacore.com
> 
> > 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.

To that, I'd object: it means, effectively, to drop support for
Windows XP, where the last Python version is 3.4.4.

We, as part of the GNU project, have no obligation to follow the
recommendations of python.org.  We should make our own decisions,
based on our goals.

  reply	other threads:[~2023-06-02 18:41 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 [this message]
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=83o7lxaeos.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).