From: Joel Sherrill <joel@rtems.org>
To: Jan Vrany <jan.vrany@fit.cvut.cz>
Cc: psmith@gnu.org, Kevin Buettner <kevinb@redhat.com>, gdb@sourceware.org
Subject: Re: Proposal: Drop GDB support for Python versions < 2.6
Date: Wed, 20 Feb 2019 21:49:00 -0000 [thread overview]
Message-ID: <CAF9ehCUj7nP2F+_LCXq2P-pPHXqyagU6pK+UkCqypFrn_+LoVw@mail.gmail.com> (raw)
In-Reply-To: <1e11ab8bf081211e6cd21f052244c834cd0f21e4.camel@fit.cvut.cz>
On Wed, Feb 20, 2019, 3:45 PM Jan Vrany <jan.vrany@fit.cvut.cz wrote:
> On Wed, 2019-02-20 at 16:29 -0500, Paul Smith wrote:
> > On Wed, 2019-02-20 at 13:45 -0700, Kevin Buettner wrote:
> > > Going even further, since 2.6 is no longer supported by the Python
> > > community, I'd also be okay with saying that GDB only supports Python
> > > 2.7 and Python 3.X.
> >
> > Don't know if anyone cares, but as a heavy user of Python support in
> > GDB, I'm fine with this. As long as GDB still supports Python 2.7 it's
> > A-OK with me.
>
> As for myself, as another user of python support, fine with me.
>
> 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.
>
Python 2.7 is shipping with at least one long-term support distribution.
While it is unlikely that anyone will notice on the native side, I know we
(RTEMS) build recent, hopefully the latest, gdb version cross.
--joel
> Just my two cents.
>
> Jan
>
>
next prev parent reply other threads:[~2019-02-20 21:49 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 [this message]
2019-02-20 22:05 ` Paul Smith
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=CAF9ehCUj7nP2F+_LCXq2P-pPHXqyagU6pK+UkCqypFrn_+LoVw@mail.gmail.com \
--to=joel@rtems.org \
--cc=gdb@sourceware.org \
--cc=jan.vrany@fit.cvut.cz \
--cc=kevinb@redhat.com \
--cc=psmith@gnu.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