public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Joel Brobecker <brobecker@adacore.com>,
	Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] gdb/python: remove Python 2 support
Date: Sun, 9 Jan 2022 21:28:10 -0500	[thread overview]
Message-ID: <b9f68176-d616-d329-a83c-c859e48e2573@polymtl.ca> (raw)
In-Reply-To: <YdlI0paJ5QIERFgl@adacore.com>

On 2022-01-08 03:18, Joel Brobecker wrote:
>>> 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.

Personally, I would also prefer merging sooner than later, just because
once it's done I can stop worrying about it.  But I am also not in a
hurry.  What finally triggered me to do this was the review of
Andrew's patch, I don't know if that is urgent or not.

Joel, I don't think that the problem is the time we leave to downstream
users who might be impacted, but how we reach them.  I like the idea of
the NEWS entry to give a heads up, because it might be the only way we
have to communicate with some downstream users.  Oh, and we could also
make it so GDB shows a warning at startup if it's built with Python 2,
saying that Python 2 support will be removed in the next version.  That
has maybe more chances of being seen.

If drop support in GDB 12, we don't have a chance to warn users (unless
we add that warning to GDB 11.2...).  We could always send an email on
the mailing lists, but that probably doesn't have as much reach.

So, if there is no particular rush, I am leaning towards aiming for GDB
13.

Simon

  reply	other threads:[~2022-01-10  2:28 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
2022-01-10  2:28     ` Simon Marchi [this message]
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=b9f68176-d616-d329-a83c-c859e48e2573@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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).