Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Use Python 2.[67] / 3.X / PEP 3118 buffer protocol
Date: Wed, 20 Feb 2019 20:49:00 -0000	[thread overview]
Message-ID: <20190220134913.3b4a730c@f29-4.lan> (raw)
In-Reply-To: <974b7419-3cbf-cf1e-256e-1724c96eb5d9@redhat.com>

On Wed, 20 Feb 2019 19:05:26 +0000
Pedro Alves <palves@redhat.com> wrote:

> On 02/19/2019 09:51 PM, Kevin Buettner wrote:
> > As noted earlier, Python 2.6, Python 2.7, and Python 3.X all have
> > support for the PEP 3118 buffer protocol.  Python releases prior
> > to 2.6 use an older buffer protocol.  Since Python 2.6 has been
> > retired for a good while now, it seems reasonable to me to remove
> > code using the older buffer protocol from GDB.
> 
> Not objecting, but I think you should send an email to gdb@ with
> a clear subject indicating that you're proposing to drop support
> for Python < 2.6.

Okay, I've done this.  See:

https://sourceware.org/ml/gdb/2019-02/msg00020.html

Kevin


  reply	other threads:[~2019-02-20 20:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 21:51 Kevin Buettner
2019-02-20 18:13 ` Tom Tromey
2019-02-26 17:47   ` Kevin Buettner
2019-02-20 19:05 ` Pedro Alves
2019-02-20 20:49   ` Kevin Buettner [this message]
2019-02-26 17:45 ` Document fact that mininum Python version is now 2.6 Kevin Buettner
2019-02-26 18:29   ` Eli Zaretskii
2019-02-27 18:18     ` Kevin Buettner
2019-02-27 19:01       ` Kevin Buettner
2019-02-27 18:17 ` [PATCH] Use Python 2.[67] / 3.X / PEP 3118 buffer protocol Kevin Buettner

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=20190220134913.3b4a730c@f29-4.lan \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@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