This is the mail archive of the
mailing list for the GDB project.
Re: Python coding style [was Re: [RFA] New python module gdb.types]
- From: Phil Muldoon <pmuldoon at redhat dot com>
- To: Doug Evans <dje at google dot com>
- Cc: Joel Brobecker <brobecker at adacore dot com>, gdb-patches at sourceware dot org
- Date: Wed, 06 Oct 2010 22:36:42 +0100
- Subject: Re: Python coding style [was Re: [RFA] New python module gdb.types]
- References: <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 <firstname.lastname@example.org> 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?
> 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.