From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: fedor_qd@mail.ru, Paul Koning <paulkoning@comcast.net>,
Tom Tromey <tom@tromey.com>,
gdb@sourceware.org
Subject: Re: Proposal to remove Python 2 support
Date: Wed, 16 Sep 2020 14:53:12 +0100 [thread overview]
Message-ID: <20200916135312.GB3030@embecosm.com> (raw)
In-Reply-To: <20200916130013.GC5797@adacore.com>
* Joel Brobecker <brobecker@adacore.com> [2020-09-16 06:00:13 -0700]:
> > That has no sense for me because Python 2 doesn't disappear from distros.
>
> I don't know how long this is going to be True, but "distros" have
> been shipping Python 3.x for quite a while now, so lack of Python 2
> support wouldn't prevent you from building GDB with Python support
> enabled.
But a user might potentially have a significant body of Python 2 code
that they run through GDB, so it's not as simple as "just" building
with Python 3 and off they go.
I think once distros start to drop Python 2 then there's a really good
argument that GDB should drop Python 2 also, but before then we need
to go in with our eyes open, if the distros still ship Python 2 then
users might be annoyed if they have to rewrite their scripts.
Thanks,
Andrew
next prev parent reply other threads:[~2020-09-16 13:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 20:46 Tom Tromey
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 [this message]
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=20200916135312.GB3030@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=brobecker@adacore.com \
--cc=fedor_qd@mail.ru \
--cc=gdb@sourceware.org \
--cc=paulkoning@comcast.net \
--cc=tom@tromey.com \
/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).