OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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.
This commit is contained in:
Tom Tromey 2018-09-08 13:37:26 -06:00
parent e7b5068cc2
commit 05c6bdc1a9
2 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/doc/ChangeLog
View File

@ -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:

6
gdb/doc/python.texi
View File

@ -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