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: Fri, 08 Oct 2010 15:17:00 -0000 [thread overview]
Message-ID: <20101008151740.GE12651@adacore.com> (raw)
In-Reply-To: <m3zkuqbfeq.fsf@redhat.com>
> My own opinion is that we should purely not opt for one particular
> flavor because there exists a vacuum. Why not follow the PEP to the
> letter? The Google guide looks sane, and really nice. But what are the
> strong feelings the project should add this particular sauce over the
> PEP? I just want to briefly examine those questions.
I think we are in a violent agreement, here. The Google guide is
interesting, not because of its (relatively short) section on formatting,
but because it gives some brief tips of things that we should or should
not do when writing Python code. My initial reaction when learning
Python was pretty negative because it wasn't the perfect language I was
lead to believe. If you read the "Learning Python" book, you'll find
that pretty much every chapter in that book has a "gotchas" section
at the end...
--
Joel
next prev parent reply other threads:[~2010-10-08 15:17 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
2010-10-07 8:01 ` Phil Muldoon
2010-10-08 15:17 ` Joel Brobecker [this message]
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=20101008151740.GE12651@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).