[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GOP-PROP 1: python formatting
From: |
Michael Welsh Duggan |
Subject: |
Re: GOP-PROP 1: python formatting |
Date: |
Sun, 05 Jun 2011 19:42:56 -0400 |
User-agent: |
Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (gnu/linux) |
Graham Percival <address@hidden> writes:
> Proposal website:
> http://lilypond.org/~graham/gop/gop_1.html
>
>
> (this proposal will be rushed because nobody will argue against
> it. Initial discussion 6 June, summary and tentative decision 8
> June, implementation 10 June)
>
> Proposal: let’s follow PEP-8.
> http://www.python.org/dev/peps/pep-0008/
>
> * use 4 spaces per indentation level
> * never max tabs and spaces
> * Code indented with a mixture of tabs and spaces should be
> converted to using spaces exclusively
For the purposes of consistency (both within Lilypond's sources, and
within code editors in general), I would modify Lilypond's version of
PEP-8 to be the slightly more strict: Never use tabs for indentation.
Only use spaces.
--
Michael Welsh Duggan
(address@hidden)
- GOP-PROP 1: python formatting, Graham Percival, 2011/06/05
- Re: GOP-PROP 1: python formatting,
Michael Welsh Duggan <=
- Re: GOP-PROP 1: python formatting, Werner LEMBERG, 2011/06/06
- Re: GOP-PROP 1: python formatting, Martin Tarenskeen, 2011/06/06
- Re: GOP-PROP 1: python formatting, Ian Hulin, 2011/06/06
- Re: GOP-PROP 1: python formatting, Patrick McCarty, 2011/06/06
- Re: GOP-PROP 1: python formatting, Trevor Daniels, 2011/06/06
- Re: GOP-PROP 1: python formatting, Karl Hammar, 2011/06/06