From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31470 invoked by alias); 6 Oct 2010 22:23:47 -0000 Received: (qmail 31462 invoked by uid 22791); 6 Oct 2010 22:23:47 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 06 Oct 2010 22:23:42 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id E7A2F2BAC3A; Wed, 6 Oct 2010 18:23:40 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id REmD6fwmw2jG; Wed, 6 Oct 2010 18:23:40 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 9A45A2BAC36; Wed, 6 Oct 2010 18:23:40 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id CE513F5895; Wed, 6 Oct 2010 15:23:37 -0700 (PDT) Date: Wed, 06 Oct 2010 22:23:00 -0000 From: Joel Brobecker To: Phil Muldoon Cc: Doug Evans , gdb-patches@sourceware.org Subject: Re: Python coding style [was Re: [RFA] New python module gdb.types] Message-ID: <20101006222337.GC2784@adacore.com> References: <4CACEBEA.1080900@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CACEBEA.1080900@redhat.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-10/txt/msg00091.txt.bz2 > 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