From: Joel Brobecker <brobecker@adacore.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: Doug Evans <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: Python coding style [was Re: [RFA] New python module gdb.types]
Date: Wed, 06 Oct 2010 22:23:00 -0000 [thread overview]
Message-ID: <20101006222337.GC2784@adacore.com> (raw)
In-Reply-To: <4CACEBEA.1080900@redhat.com>
> My deeply biased and very personal ideology her e is if how emacs
> handles it.
I think it would be wrong to adopt that philosophy, and to be honest,
I'm getting a little tired about having to suffer certain decisions
purely because this is the default emacs indentation style. Even
if I did use emacs, I just think it's more important to be consistent
with the rest of the Python community.
There is actually an official Python Coding Style, called PEP8:
http://www.python.org/dev/peps/pep-0008/
I think we should strive to not break whatever suggestions this guide
provides, and add some extra of our own if we feel necessary.
I looked at the Google Python Style Guide, and it does not conflict
with PEP8. I also have relatively limited knowledge of Python, but
I absolutely agree with everything in that document.
--
Joel
next prev parent reply other threads:[~2010-10-06 22:23 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
2010-10-06 22:23 ` Joel Brobecker [this message]
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=20101006222337.GC2784@adacore.com \
--to=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).