From: Paul Koning <paulkoning@comcast.net>
To: Kevin Buettner <kevinb@redhat.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Proposal: Drop GDB support for Python versions < 2.6
Date: Wed, 20 Feb 2019 22:06:00 -0000 [thread overview]
Message-ID: <3A227E41-CC9A-43FF-A526-81FD325215E1@comcast.net> (raw)
In-Reply-To: <b7af208f7e163c236f92c7b728804cfe06411303.camel@gnu.org>
> On Feb 20, 2019, at 4:29 PM, Paul Smith <psmith@gnu.org> 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.
I concur.
Along the same lines, do you want to drop support for <= 3.x for some x? Python 3 is up to 3.7 now; I'm not sure if it matters much to the code or maintenance burden, but dropping support for some of the older 3.x releases might also make sense.
paul
next prev parent reply other threads:[~2019-02-20 22:06 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
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 [this message]
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=3A227E41-CC9A-43FF-A526-81FD325215E1@comcast.net \
--to=paulkoning@comcast.net \
--cc=gdb@sourceware.org \
--cc=kevinb@redhat.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