This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Python 3 vs. @code{Python} 3 in python.texi
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Yao Qi <qiyaoltc at gmail dot com>
- Cc: tim dot wiederhake at intel dot com, gdb-patches at sourceware dot org
- Date: Mon, 20 Mar 2017 20:22:01 +0200
- Subject: Re: Python 3 vs. @code{Python} 3 in python.texi
- Authentication-results: sourceware.org; auth=none
- References: <CAH=s-PMYaTJ3CdYSiNODsdD-i6GMcRf6ogv5hWuAf5H4sWNe4g@mail.gmail.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Yao Qi <qiyaoltc@gmail.com>
> Date: Mon, 20 Mar 2017 14:36:42 +0000
> Cc: Tim Wiederhake <tim.wiederhake@intel.com>,
> "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>
> 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."
There's no reason to use @code for Python the name of a programming
language. If we do that in the manual, that is a mistake.
For 'python' the program, we should use @command{python}, not @code.