From: Eli Zaretskii <eliz@gnu.org>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: tim.wiederhake@intel.com, gdb-patches@sourceware.org
Subject: Re: Python 3 vs. @code{Python} 3 in python.texi
Date: Mon, 20 Mar 2017 18:22:00 -0000 [thread overview]
Message-ID: <83mvcfx0za.fsf@gnu.org> (raw)
In-Reply-To: <CAH=s-PMYaTJ3CdYSiNODsdD-i6GMcRf6ogv5hWuAf5H4sWNe4g@mail.gmail.com> (message from Yao Qi on Mon, 20 Mar 2017 14:36:42 +0000)
> 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.
next prev parent reply other threads:[~2017-03-20 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 14:36 Yao Qi
2017-03-20 18:22 ` Eli Zaretskii [this message]
2017-03-22 12:43 ` [PATCH] Remove @code for python Yao Qi
2017-03-22 15:39 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mvcfx0za.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
--cc=tim.wiederhake@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox