From: Tom Tromey <tom@tromey.com>
To: gdb@sourceware.org
Subject: Proposal to remove Python 2 support
Date: Tue, 15 Sep 2020 14:46:20 -0600 [thread overview]
Message-ID: <87sgbiahur.fsf@tromey.com> (raw)
Hi. Python 2 officially reached its sunset date this year:
https://www.python.org/doc/sunset-python-2/
I think gdb should follow suit starting in gdb 11 -- that is, my
proposal is to keep Python 2 support for the upcoming gdb 10 release,
but remove said support from git master.
In the short term this would amount to some relatively minor code
cleanups.
In the longer term, my preferred approach to handling inferior control
from Python is to base it on async/await, which IIUC is only available
in Python 3. So, this would be an enabling step.
Let me know what you think.
Tom
next reply other threads:[~2020-09-15 20:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 20:46 Tom Tromey [this message]
2020-09-15 20:58 ` Paul Koning
2020-09-15 22:54 ` Re[2]: " fedor_qd
2020-09-16 13:00 ` Joel Brobecker
2020-09-16 13:53 ` Andrew Burgess
2020-09-16 15:03 ` Paul Koning
2020-09-16 15:23 ` Joel Brobecker
2020-09-16 15:34 ` Andrew Burgess
2020-09-17 17:07 ` Tom Tromey
2020-09-17 17:49 ` Joel Brobecker
2020-09-17 18:03 ` Eli Zaretskii
2020-09-17 18:10 ` Jan Kratochvil
2020-09-17 18:45 ` Eli Zaretskii
2020-09-18 7:15 ` vincent Dupaquis
2020-09-18 7:25 ` Eli Zaretskii
2020-09-17 18:16 ` Joel Brobecker
2020-09-16 15:44 ` Eli Zaretskii
2020-09-16 17:50 ` André Pönitz
2020-09-17 17:03 ` Tom Tromey
2020-09-18 15:59 ` Pedro Alves
2020-09-18 16:39 ` Mikhail.Terekhov
2020-09-18 16:55 ` Tom Tromey
2020-09-18 17:13 ` Mikhail.Terekhov
2020-09-18 17:35 ` Pedro Alves
2020-09-18 19:20 ` Jeffrey Walton
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=87sgbiahur.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb@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).