From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: Document fact that mininum Python version is now 2.6
Date: Wed, 27 Feb 2019 19:01:00 -0000 [thread overview]
Message-ID: <20190227120041.0ec5ca7c@f29-4.lan> (raw)
In-Reply-To: <20190227111809.157d6f9c@f29-4.lan>
On Wed, 27 Feb 2019 11:18:09 -0700
Kevin Buettner <kevinb@redhat.com> wrote:
> > > gdb/ChangeLog:
> > >
> > > * NEWS: Note minimum Python version.
> > >
> > > gdb/doc/ChangeLog:
> > >
> > > * gdb.texinfo (Configure Options): Document minimum python
> > > version.
> >
> > Thanks, this is OK.
>
> Thanks for the review.
>
> I've pushed this change.
I realized that, in conjunction with Joel's changes to the NEWS file,
this push now says that gdb-8.3 no longer supports Python versions
less than 2.6. This is technically true due to the commit of the
two argument version of gdb.Value that I pushed yesterday.
(That commit uses the PEP 3118 buffer protocol which is only
supported in Python versions 2.6 and up.)
So...
I've pushed this documentation commit to gdb-8.3-branch also.
I won't push "Use Python 2.[67] / 3.X / PEP 3118 buffer protocol"
to the gdb-8.3-branch unless someone asks for it though.
Kevin
next prev parent reply other threads:[~2019-02-27 19:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 21:51 [PATCH] Use Python 2.[67] / 3.X / PEP 3118 buffer protocol 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
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 [this message]
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=20190227120041.0ec5ca7c@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