From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] gdb/python: drop support for Python < 3.4
Date: Fri, 07 Jan 2022 18:33:05 +0200 [thread overview]
Message-ID: <83tuef4ibi.fsf@gnu.org> (raw)
In-Reply-To: <20220107152921.2858909-3-simon.marchi@polymtl.ca> (message from Simon Marchi via Gdb-patches on Fri, 7 Jan 2022 10:29:21 -0500)
> Date: Fri, 7 Jan 2022 10:29:21 -0500
> From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
>
> Python 3 versions <= 3.3 are quite old and not likely to be used
> nowadays. Dropping support for them allows us to remove some hacks and
> compatibility macros that depend on the Python version being < 3.4.
Are there real reasons to drop those old versions? I mean, does
supporting them causes us some real maintenance burden?
> We could go even further and document that we only support versions 3.5
> or 3.6 and up, for example, but that wouldn't change the code.
That'd mean dropping support for Windows XP, as AFAIU 3.4 is the last
one which supports it.
next prev parent reply other threads:[~2022-01-07 16:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 15:29 [PATCH 1/3] gdb/python: remove Python 2 support Simon Marchi
2022-01-07 15:29 ` [PATCH 2/3] gdb/python: remove Python 2/3 compatibility macros Simon Marchi
2022-01-07 15:29 ` [PATCH 3/3] gdb/python: drop support for Python < 3.4 Simon Marchi
2022-01-07 16:33 ` Eli Zaretskii [this message]
2022-01-07 17:14 ` Simon Marchi
2022-01-07 15:33 ` [PATCH 1/3] gdb/python: remove Python 2 support Paul Koning
2022-01-07 15:41 ` Simon Marchi
2022-01-07 17:44 ` Andrew Burgess
2022-01-08 8:18 ` Joel Brobecker
2022-01-10 2:28 ` Simon Marchi
2022-01-10 2:59 ` Joel Brobecker
2022-01-10 16:39 ` Simon Marchi
2022-01-11 3:26 ` Joel Brobecker
2022-01-10 16:26 ` Tom Tromey
2022-03-03 16:31 ` Andrew Burgess
2022-03-03 17:40 ` Simon Marchi
2022-03-21 14:46 ` [PATCH v2 0/2] Remove " Simon Marchi
2022-03-21 14:46 ` [PATCH v2 1/2] gdb/python: remove " Simon Marchi
2022-03-21 14:50 ` Simon Marchi
2022-03-21 14:58 ` Eli Zaretskii
2022-03-21 15:04 ` Simon Marchi
2022-03-21 15:33 ` Pedro Alves
2022-03-21 16:31 ` Simon Marchi
2022-03-21 16:55 ` Pedro Alves
2022-03-21 17:04 ` Simon Marchi
2022-03-21 14:46 ` [PATCH v2 2/2] gdb/python: remove Python 2/3 compatibility macros Simon Marchi
2022-03-23 11:46 ` [PATCH v2 0/2] Remove Python 2 support Simon Marchi
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=83tuef4ibi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).