Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>, gdb@sourceware.org
Subject: Re: Proposal: Drop GDB support for Python versions < 2.6
Date: Thu, 21 Feb 2019 06:46:00 -0000	[thread overview]
Message-ID: <20190220234610.6d8db6c7@f29-4.lan> (raw)
In-Reply-To: <83a7iphkjb.fsf@gnu.org>

On Thu, 21 Feb 2019 05:45:12 +0200
Eli Zaretskii <eliz@gnu.org> wrote:

> > Date: Thu, 21 Feb 2019 06:39:04 +0400
> > From: Joel Brobecker <brobecker@adacore.com>
> > Cc: Kevin Buettner <kevinb@redhat.com>, gdb@sourceware.org
> >   
> > > > 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.  
> > 
> > +1.
> > 
> > As for Python 2.7, let's keep it for a year or two more, before
> > we completely drop it.  
> 
> Dropping 2.6, let alone 2.7, would be a terrible nuisance for me.  So
> I'm asking to keep that until they really put a drag on the GDB
> development (which doesn't seem to be the case now).

That's fine.  At the moment, there's no real reason to not continue to
(potentially) support 2.6.  I say "potentially" because for some of us,
figuring out how to test against 2.6 is really hard.  However, if you
continue to do regular builds of upstream gdb using Python 2.6,
it'll get tested.

Kevin


  reply	other threads:[~2019-02-21  6:46 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
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 [this message]
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=20190220234610.6d8db6c7@f29-4.lan \
    --to=kevinb@redhat.com \
    --cc=eliz@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