From: Eli Zaretskii <eliz@gnu.org>
To: vincent Dupaquis <v.dupaquis@trusted-objects.com>
Cc: gdb@sourceware.org
Subject: Re: Proposal to remove Python 2 support
Date: Fri, 18 Sep 2020 10:25:03 +0300 [thread overview]
Message-ID: <83a6xn5yy8.fsf@gnu.org> (raw)
In-Reply-To: <d3ee0e62-050b-e83e-c3a8-153a5867b087@trusted-objects.com> (message from vincent Dupaquis on Fri, 18 Sep 2020 09:15:35 +0200)
> From: vincent Dupaquis <v.dupaquis@trusted-objects.com>
> Date: Fri, 18 Sep 2020 09:15:35 +0200
>
> Some vendors are still delivering gdb with python2 by default, for
> instance ARM in their arm-none-eabi delivery
> (https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads).
To clarify, I didn't mean to say that we should decide not to have new
features supported for Python 2. What I wrote was written in response
to an opinion that keeping Python 2 supported might induce some heavy
development and maintenance costs. I then said that we could decide
not to support some of the newer features for Python 2, because doing
that would be better than dropping Python 2 support completely.
FTR, I'm the last person to be happy with dropping Python 2 support: I
have it installed, and I'm building GDB with Python 2. I even
volunteered to be the tester of Python 2.6 usage in GDB, because that
is even older.
next prev parent reply other threads:[~2020-09-18 7:24 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
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 [this message]
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=83a6xn5yy8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=v.dupaquis@trusted-objects.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).