From: Joel Brobecker <brobecker@adacore.com>
To: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@polymtl.ca>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH 1/3] gdb/python: remove Python 2 support
Date: Sat, 8 Jan 2022 12:18:26 +0400 [thread overview]
Message-ID: <YdlI0paJ5QIERFgl@adacore.com> (raw)
In-Reply-To: <20220107174405.GC622389@redhat.com>
> > 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).
>
> Given this is a pretty big change (if you are a user that happens to
> build against Py2), I wonder if it would be worth holding off this
> change until after GDB 12 has branched?
FWIW, if it were me proposing the patch, I'd ask that we go ahead
now. Delaying patches always comes at a cost, and while I'm sympathetic
to those few who might not be ready to move to Python 3.x yet,
they can continue using GDB 11 if needed. Meanwhile, I'm hoping
to start discussions about GDB 12 a couple of weeks from now,
and it's typically taken us a couple of months before we reach
a point where we can branch, and then another month or two,
sometimes more, before the first release is out. So those who
still depend on Python 2.x have those many months to finish
their transition.
--
Joel
next prev parent reply other threads:[~2022-01-08 8:18 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 ` [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 [this message]
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=YdlI0paJ5QIERFgl@adacore.com \
--to=brobecker@adacore.com \
--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).