Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb@sourceware.org, apoenitz@t-online.de
Subject: Re: Proposal: Drop GDB support for Python versions < 2.6
Date: Thu, 21 Feb 2019 14:40:00 -0000	[thread overview]
Message-ID: <8336ohgq8d.fsf@gnu.org> (raw)
In-Reply-To: <20190220233915.30b52f4c@f29-4.lan> (message from Kevin Buettner	on Wed, 20 Feb 2019 23:39:15 -0700)

> Date: Wed, 20 Feb 2019 23:39:15 -0700
> From: Kevin Buettner <kevinb@redhat.com>
> Cc: André Pönitz <apoenitz@t-online.de>
> 
> I think we can drop Python 2.7 (and lower) sometime after the major
> Linux distributions start defaulting to python 3.X for the "python"
> command.

I'd appreciate if we did that, thanks.

To clarify, dropping 2.x would not be a catastrophe for me.  Just a
nuisance.  But a significant one.  But nuisance.


  reply	other threads:[~2019-02-21 14:40 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 [this message]
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=8336ohgq8d.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=apoenitz@t-online.de \
    --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