Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
* Python 3 vs. @code{Python} 3 in python.texi
@ 2017-03-20 14:36 Yao Qi
  2017-03-20 18:22 ` Eli Zaretskii
  0 siblings, 1 reply; 4+ messages in thread
From: Yao Qi @ 2017-03-20 14:36 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: Tim Wiederhake, gdb-patches

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 (齐尧)


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2017-03-22 15:39 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-20 14:36 Python 3 vs. @code{Python} 3 in python.texi Yao Qi
2017-03-20 18:22 ` Eli Zaretskii
2017-03-22 12:43   ` [PATCH] Remove @code for python Yao Qi
2017-03-22 15:39     ` Eli Zaretskii

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox