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 0baaf93..c83b5f5 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,5 +1,10 @@
 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:
        * python.texi (Unwinding Frames in Python): Rewrite
        create_unwind_info documentation.  Update read_register

diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
index ccad593..eb4c3a5 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