gwibber-team team mailing list archive
-
gwibber-team team
-
Mailing list archive
-
Message #00034
Re: Coding standards
2009/5/6 Ryan Paul <segphault@xxxxxxxxxxxxxxx>:
> I believe that most of us in the Gwibber team favor two-space
> indentation. I personally think that it's much more conducive to
> readability.
Really? I find it quite the opposite. It's far easier to discern
indentation levels with 4-space indents than with 2, IME. (Of course,
this was the beauty of tabs-for-indents; you could set it however you
liked it. However tabs, spaces and Python don't mix well).
I stupidly forgot to include a link to PEP 8 in my last message,
despite quoting it. It's here:
http://www.python.org/dev/peps/pep-0008/. I'm used to following this
when working with Python code, which is why I asked the question.
However, I'm perfectly happy to follow whatever coding guidelines are
set by the project. I'm not trying to make waves here.
> Aside from that, we don't really have any official standards. I don't
> object to a lack of consistency on other matters and I generally think
> it's fine to let individual contributors write code in the manner that
> they are most comfortable with.
>
> I'm open to having further discussion on this issue if you or others on
> this list have additional feedback or feel differently. If you think
> that the lack of consistency is creating a barrier to entry for
> potential contributors, then it might be worthwhile to consider more
> rigid guidelines.
>
Having standards makes it easier for people to contribute to a
codebase because it ensures that everyone's writing code in the same
way, following the same conventions and using a common set of idioms.
That makes the code clearer to everyone involved and, IME, lowers the
barrier to entry.
Cheers,
Graham
--
Graham Binns | PGP Key: 4DAD18FA
References