From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Joel Brobecker <brobecker@adacore.com>,
paulkoning@comcast.net, tom@tromey.com, gdb@sourceware.org
Subject: Re: Proposal to remove Python 2 support
Date: Thu, 17 Sep 2020 20:10:05 +0200 [thread overview]
Message-ID: <20200917181005.GA2839196@host1.jankratochvil.net> (raw)
In-Reply-To: <83o8m45lih.fsf@gnu.org>
On Thu, 17 Sep 2020 20:03:02 +0200, Eli Zaretskii wrote:
> But that kind of thing is inevitable when one relies on external
> libraries for some of our features. For example, suppose that the
> source-highlight package learns to highlight sources better -- these
> improvements will only available to users if they upgrade their
> installed source-highlight library before building GDB.
That is different.
There will always be installed only one version of source-highlight package.
With Python there can be (and currently commonly is) installed both Python
2 & 3 and it is sometimes tricky to convince a package to use the other
version than the one it uses by default.
Jan
next prev parent reply other threads:[~2020-09-17 18:10 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 [this message]
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=20200917181005.GA2839196@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--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).