From: Matt Rice <ratmice@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul_Koning@dell.com, gdb-patches@sourceware.org
Subject: Re: Doc: make python function/method descriptions look as in Python
Date: Sat, 03 Sep 2011 21:53:00 -0000 [thread overview]
Message-ID: <CACTLOFoJc7icubLEvBjNQkwgzkvo31VcVFwcJxEb-po1NuGYMg@mail.gmail.com> (raw)
In-Reply-To: <837h5p2a6g.fsf@gnu.org>
On Sat, Sep 3, 2011 at 3:27 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: <Paul_Koning@Dell.com>
>> Date: Thu, 1 Sep 2011 15:52:59 -0500
>>
>> I found the descriptions of the Python methods/functions hard to read because they are not shown in Python syntax.
>
> I have no opinion on whether this is desirable or not; I will go with
> whatever others think. Python is a read-only language for me.
I too find the existing method syntax awkward, and prefer it with all
the parens/brackets
next prev parent reply other threads:[~2011-09-03 19:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 21:23 Paul_Koning
2011-09-02 12:26 ` Pedro Alves
2011-09-02 16:45 ` Paul_Koning
2011-09-02 17:08 ` Pedro Alves
2011-09-03 19:46 ` Eli Zaretskii
2011-09-03 21:53 ` Matt Rice [this message]
2011-09-04 8:38 ` Paul_Koning
2011-09-04 10:37 ` Eli Zaretskii
2011-09-06 15:42 ` Paul_Koning
[not found] ` <09787EF419216C41A903FD14EE5506DD01534916B2@AUSX7MCPC103.AMER.DELL.COM>
2011-09-06 18:01 ` Paul Koning
2011-09-09 21:15 ` Paul Koning
2011-09-09 21:33 ` Eli Zaretskii
2011-09-15 17:19 ` Paul_Koning
2011-10-21 14:17 ` Kevin Pouget
2011-10-21 15:51 ` Tom Tromey
2011-09-06 19:39 ` Phil Muldoon
2011-09-06 19:45 ` Paul_Koning
2011-09-06 19:57 ` Paul_Koning
2011-09-06 20:07 ` Eli Zaretskii
2011-09-06 20:25 ` Paul_Koning
2011-09-07 0:45 ` Eli Zaretskii
2011-09-06 19:56 ` Eli Zaretskii
2011-09-06 20:01 ` Paul_Koning
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=CACTLOFoJc7icubLEvBjNQkwgzkvo31VcVFwcJxEb-po1NuGYMg@mail.gmail.com \
--to=ratmice@gmail.com \
--cc=Paul_Koning@dell.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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