From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Document fact that mininum Python version is now 2.6
Date: Tue, 26 Feb 2019 17:45:00 -0000 [thread overview]
Message-ID: <20190226104533.601164f1@f29-4.lan> (raw)
In-Reply-To: <20190219145110.03bccce6@f29-4.lan>
gdb/ChangeLog:
* NEWS: Note minimum Python version.
gdb/doc/ChangeLog:
* gdb.texinfo (Configure Options): Document minimum python
version.
diff --git a/gdb/NEWS b/gdb/NEWS
index bfb023e7bb..e2f1907db4 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -188,6 +188,8 @@ FreeBSD/riscv riscv*-*-freebsd*
* Python API
+ ** GDB no longer supports Python versions less than 2.6.
+
** The gdb.Inferior type has a new 'progspace' property, which is the program
space associated to that inferior.
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 7b2e5578bd..8b61cc1ba3 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -35975,7 +35975,7 @@ libpython is present and found at configure time.) Python makes
@value{GDBN} scripting much more powerful than the restricted CLI
scripting language. If your host does not have Python installed, you
can find it on `http://www.python.org/download/'. The oldest version
-of Python supported by GDB is 2.4. The optional argument @var{python}
+of Python supported by GDB is 2.6. The optional argument @var{python}
is used to find the Python headers and libraries. It can be either
the name of a Python executable, or the name of the directory in which
Python is installed.
next prev parent reply other threads:[~2019-02-26 17:45 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 ` Kevin Buettner [this message]
2019-02-26 18:29 ` Document fact that mininum Python version is now 2.6 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=20190226104533.601164f1@f29-4.lan \
--to=kevinb@redhat.com \
--cc=eliz@gnu.org \
--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