This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Python 3 vs. @code{Python} 3 in python.texi
- From: Yao Qi <qiyaoltc at gmail dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: Tim Wiederhake <tim dot wiederhake at intel dot com>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Mon, 20 Mar 2017 14:36:42 +0000
- Subject: Python 3 vs. @code{Python} 3 in python.texi
- Authentication-results: sourceware.org; auth=none
Hi Eli,
Which one do we use in sentence "In XXX, the return
value is a @code{memoryview} object.", "Python 3" or
"@code{Python} 3"?
https://sourceware.org/ml/gdb-patches/2017-03/msg00039.html
We use "@code{Python} 3" for Inferior.read_memory,
....
@code{Inferior.write_memory} function. In @code{Python} 3, the return
value is a @code{memoryview} object.
so I suggested that we need to use "@code{Python} 3" for
consistency, but Tim believes "Python 3" should be used,
because "@code{python} is used when the actual "python" command
in GDB is meant, not the name of the language per-se."
--
Yao (齐尧)