Re: [PATCH 1/3] gdb/python: remove Python 2 support

[Simon Marchi <simon.marchi@polymtl.ca>]

On 2022-01-09 21:59, Joel Brobecker wrote:
>> 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.
> 
> If you do not mind, then, OK for me as well. But just in the spirit of
> exploring all our options: What about adding a warning in the 11.2 NEWS?
> We create a PR, add news entry, and the change is in both the NEWS and
> the announcement I'm sending to everyone. We can also add a dedicated
> NEWS entry on GDB's web page.

Even though it would be possible to add the deprecation notice in 11.2,
I don't think we should.  I see Python 2 getting the "will be removed in
next release" a bit like a new feature, and we should not introduce it
in a bugfix release.

Simon