From: Jeffrey Walton <noloader@gmail.com>
To: gdb@sourceware.org
Subject: Re: Proposal to remove Python 2 support
Date: Fri, 18 Sep 2020 15:20:14 -0400 [thread overview]
Message-ID: <CAH8yC8n4bZ6huGUz5LQ+YJ10FJJXVWwtphKU7gmVyMLrAdZG-Q@mail.gmail.com> (raw)
In-Reply-To: <87pn6j58j9.fsf@tromey.com>
On Fri, Sep 18, 2020 at 12:56 PM Tom Tromey <tom@tromey.com> wrote:
>
> 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.
>
> Does anyone know if there are other distros with LTS releases that do
> this? I guess it makes sense to hold off for those; at least major
> distros anyway.
Ubuntu 16.04 is LTS, and it is also ESM. ESM is Extended Security
Maintenance. The ESM means it will probably be around for 2 or 3 years
beyond the 5 years provided by LTS (i.e., 2023 or so).
It looks like Ubuntu 16.04 provides both Python 2.7 and 3.5.
https://packages.ubuntu.com/xenial/python/.
It looks like Ubuntu 16's GDB is built against Python 3.5.
https://packages.ubuntu.com/xenial/devel/gdb.
Jeff
prev parent reply other threads:[~2020-09-18 19:20 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
2020-09-18 19:20 ` Jeffrey Walton [this message]
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=CAH8yC8n4bZ6huGUz5LQ+YJ10FJJXVWwtphKU7gmVyMLrAdZG-Q@mail.gmail.com \
--to=noloader@gmail.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).