From: Phil Muldoon <pmuldoon@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: Python coding style [was Re: [RFA] New python module gdb.types]
Date: Wed, 06 Oct 2010 21:37:00 -0000 [thread overview]
Message-ID: <4CACEBEA.1080900@redhat.com> (raw)
In-Reply-To: <AANLkTikM7Sdn6-LS9psAM92HaWtdr54qKz_zUaz7Jggb@mail.gmail.com>
On 10/06/2010 10:20 PM, Doug Evans wrote:
> [note new subject line]
>
> On Wed, Oct 6, 2010 at 2:11 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>> The python style is to not have a space before the opening parenthesis.
>> [...]
>> I think we should try to follow the Python style because it makes it
>> easier for Python users to read our code.
>
> Can we, at least as a first pass, adopt this?
>
> http://google-styleguide.googlecode.com/svn/trunk/pyguide.html
>
> Then I don't have to continually switch modes. :-)
>
> [There may be parts that aren't applicable here, but as a first pass,
> it's a good start.]
My deeply biased and very personal ideology her e is if how emacs
handles it. Granted it is not the best representer of python style.
For my 2 pence worth, if the google style somehow replicates the emacs
representation of Python code, all the better. OTOH I'm not sure if
any GNU standards represent Python at all. Certainley the
libstdc++ printers are a little liberal wtih Python styles.
Cheers
Phil
next prev parent reply other threads:[~2010-10-06 21:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 21:21 Doug Evans
2010-10-06 21:37 ` Phil Muldoon [this message]
2010-10-06 22:23 ` Joel Brobecker
2010-10-07 8:01 ` Phil Muldoon
2010-10-08 15:17 ` Joel Brobecker
2010-10-06 22:25 ` Python coding style Tom Tromey
2010-10-08 21:20 ` Doug Evans
2010-10-08 21:35 ` Tom Tromey
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=4CACEBEA.1080900@redhat.com \
--to=pmuldoon@redhat.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).