From: Pedro Alves <pedro@palves.net>
To: Mikhail.Terekhov@dell.com, tom@tromey.com
Cc: gdb@sourceware.org
Subject: Re: Proposal to remove Python 2 support
Date: Fri, 18 Sep 2020 18:35:14 +0100 [thread overview]
Message-ID: <afa32950-e4b9-de28-7c43-9dde6412a006@palves.net> (raw)
In-Reply-To: <cf7c9e4cc7504ddabd4866cbfdc1723e@x13pwdurdag1107.AMER.DELL.COM>
On 9/18/20 6:13 PM, Mikhail.Terekhov--- via Gdb wrote:
>> From: Gdb <gdb-bounces@sourceware.org> On Behalf Of Tom Tromey
>>
>> Pedro> Dropping Python 2 support is going to be an issue for us, given
>> Pedro> we will still have a couple years more of DTS releases for RHEL
>> Pedro> 7, which is Python 2.7 based.
>>
>>>> RHEL 7 comes with Python 3.6 as well.
>>
>> I think the issue must be that gdb is built against Python 2 on RHEL 7.
>
> If they would want to update to the new major version of gdb they would build it with Python3. What is the problem?
It would break compatibility with pretty printers, user scripts, and
require Python3 versions of Python libraries scripts may load.
Pedro Alves
next prev parent reply other threads:[~2020-09-18 17:35 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
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 [this message]
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=afa32950-e4b9-de28-7c43-9dde6412a006@palves.net \
--to=pedro@palves.net \
--cc=Mikhail.Terekhov@dell.com \
--cc=gdb@sourceware.org \
--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).