From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6729 invoked by alias); 6 Oct 2010 21:37:18 -0000 Received: (qmail 6717 invoked by uid 22791); 6 Oct 2010 21:37:17 -0000 X-SWARE-Spam-Status: No, hits=-5.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 06 Oct 2010 21:37:12 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o96LakPi017592 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 6 Oct 2010 17:36:47 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id o96LakdN022631; Wed, 6 Oct 2010 17:36:46 -0400 Received: from localhost.localdomain (ovpn-113-109.phx2.redhat.com [10.3.113.109]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id o96Lahbc008795; Wed, 6 Oct 2010 17:36:44 -0400 Message-ID: <4CACEBEA.1080900@redhat.com> Date: Wed, 06 Oct 2010 21:37:00 -0000 From: Phil Muldoon User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100921 Fedora/3.1.4-1.fc13 Thunderbird/3.1.4 MIME-Version: 1.0 To: Doug Evans CC: Joel Brobecker , gdb-patches@sourceware.org Subject: Re: Python coding style [was Re: [RFA] New python module gdb.types] References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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/msg00089.txt.bz2 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 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