Mention Python versions in the documentation

This updates python.texi to note that gdb can be compiled against
either major version of Python.  It also removes the "execfile"
example, because that is specific to Python 2.

gdb/doc/ChangeLog
2018-09-10  Tom Tromey  <tom@tromey.com>

	* python.texi (Python): Mention Python versions.  Don't mention
	execfile.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 0baaf93609ad595c66827d0f435ee776c5119287..c83b5f5d8040ddcde8df07d7e31c00a63cfeb7b4 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,8 @@
+2018-09-10  Tom Tromey  <tom@tromey.com>
+
+       * python.texi (Python): Mention Python versions.  Don't mention
+       execfile.
+
 2018-09-10  Tom Tromey  <tom@tromey.com>
 
        PR python/19808:

diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
index ccad593e247480757fa3c5667968ae324656f618..eb4c3a53781e4cfd9c6d2824e0e7ac43ec390dea 100644 (file)
--- a/gdb/doc/python.texi
+++ b/gdb/doc/python.texi
@@ -18,6 +18,8 @@
 You can extend @value{GDBN} using the @uref{http://www.python.org/,
 Python programming language}.  This feature is available only if
 @value{GDBN} was configured using @option{--with-python}.
+@value{GDBN} can be built against either Python 2 or Python 3; which
+one you have depends on this configure-time option.
 
 @cindex python directory
 Python scripts used by @value{GDBN} should be installed in
@@ -113,10 +115,6 @@ interpreter:
 The script name must end with @samp{.py} and @value{GDBN} must be configured
 to recognize the script language based on filename extension using
 the @code{script-extension} setting.  @xref{Extending GDB, ,Extending GDB}.
-
-@item python execfile ("script-name")
-This method is based on the @code{execfile} Python built-in function,
-and thus is always available.
 @end table
 
 @node Python API