From: Paul Smith <psmith@gnu.org>
To: gdb@sourceware.org
Subject: Re: Proposal: Drop GDB support for Python versions < 2.6
Date: Wed, 20 Feb 2019 22:05:00 -0000 [thread overview]
Message-ID: <4df03e9038ffc301b771ad1249138cecf1083236.camel@gnu.org> (raw)
In-Reply-To: <1e11ab8bf081211e6cd21f052244c834cd0f21e4.camel@fit.cvut.cz>
On Wed, 2019-02-20 at 21:44 +0000, Jan Vrany wrote:
> Actually, I'd even be fine with more radical move, dropping support
> for 2.x altogether. Python 2.7 support will end in less a year
> from now anyway.
I expected someone to say this :).
I'm well aware of the EOL pan for Python 2.7, obviously. However, I
cannot begin to guess when we'll stop using it internally due to the
massive (and 100% unproductive) overhead involved with transitioning to
Python 3. We only use Python (and GDB!) internally, and we build it
ourselves we don't use a version that comes with our distribution, so
it doesn't really matter to us how well supported it is externally.
So, I would be unhappy if support for Python 2.7 were dropped.
However, when it becomes a big burden for GDB devs to support it I
guess we'll have to do something else (build Python 3 just for GDB?)
Again, just speaking as a user, not a GDB developer.
next prev parent reply other threads:[~2019-02-20 22:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 20:45 Kevin Buettner
2019-02-20 21:30 ` Paul Smith
2019-02-20 21:44 ` Jan Vrany
2019-02-20 21:49 ` Joel Sherrill
2019-02-20 22:05 ` Paul Smith [this message]
2019-02-20 22:11 ` Kevin Buettner
2019-02-20 23:26 ` André Pönitz
2019-02-21 6:39 ` Kevin Buettner
2019-02-21 14:40 ` Eli Zaretskii
2019-02-21 18:35 ` André Pönitz
2019-02-21 18:52 ` John Baldwin
2019-02-21 9:10 ` Dmitry Samersoff
2019-02-20 22:06 ` Paul Koning
2019-02-21 17:11 ` Tom Tromey
2019-02-20 22:58 ` André Pönitz
2019-02-21 2:39 ` Joel Brobecker
2019-02-21 3:46 ` Eli Zaretskii
2019-02-21 6:46 ` Kevin Buettner
2019-02-21 14:42 ` Eli Zaretskii
2019-02-21 10:45 ` Mark Wielaard
2019-02-21 3:40 ` Eli Zaretskii
2019-02-21 17:55 ` Pedro Alves
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=4df03e9038ffc301b771ad1249138cecf1083236.camel@gnu.org \
--to=psmith@gnu.org \
--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