From: Paul Koning <paulkoning@comcast.net>
To: Simon Marchi <simon.marchi@polymtl.ca>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] gdb/python: remove Python 2 support
Date: Fri, 7 Jan 2022 10:33:33 -0500 [thread overview]
Message-ID: <70D21D56-32F2-437C-AB7A-2093F2C6BFD2@comcast.net> (raw)
In-Reply-To: <20220107152921.2858909-1-simon.marchi@polymtl.ca>
> On Jan 7, 2022, at 10:29 AM, Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> wrote:
>
> Support for Python 2 is a maintenance burden for any patches touching
> Python support. Among others, the differences between Python 2 and 3
> string and integer types are subtle. It requires a lot of effort and
> thinking to get something that behaves correctly on both. And that's if
> the author and reviewer of the patch even remember to test with Python
> 2.
>
> See this thread for an example:
>
> https://sourceware.org/pipermail/gdb-patches/2021-December/184260.html
>
> I therefore propose to drop Python 2 support. I know that a few
> maintainers have given their informal support for this (on IRC and the
> mailing list).
It sounds like a good change to me.
> ...
> I did not update the configure script more than just removing the
> explicit references to Python 2. We could maybe do more there, like
> check the Python version and reject it if that version is not
> supported.
How hard is that? It seems worth having such a check.
paul
next prev parent reply other threads:[~2022-01-07 15:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 15:29 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
2022-01-07 17:14 ` Simon Marchi
2022-01-07 15:33 ` Paul Koning [this message]
2022-01-07 15:41 ` [PATCH 1/3] gdb/python: remove Python 2 support 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=70D21D56-32F2-437C-AB7A-2093F2C6BFD2@comcast.net \
--to=paulkoning@comcast.net \
--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).