From bde5d50a10ab68e864c161fb98478c3803b6d409 Mon Sep 17 00:00:00 2001 From: Graham Percival Date: Thu, 23 Jun 2011 23:42:58 +0100 Subject: [PATCH] CG: add final GOP-POPR 1: python formatting --- .../contributor/administration.itexi | 29 +++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/Documentation/contributor/administration.itexi b/Documentation/contributor/administration.itexi index aef67b3bea..f6cf38194c 100644 --- a/Documentation/contributor/administration.itexi +++ b/Documentation/contributor/administration.itexi @@ -163,6 +163,7 @@ difficult tasks. * Motivation:: * Ongoing jobs:: * Policy decisions:: +* Policy decisions (finished):: @end menu @node Motivation @@ -506,6 +507,34 @@ amount of current material in either form, are important. @end itemize +@node Policy decisions (finished) +@subsection Policy decisions (finished) + +@subheading GOP-PROP 1: python formatting + +We will follow the indentation described in PEP-8. +@uref{http://www.python.org/dev/peps/pep-0008/} + +@itemize +@item +use 4 spaces per indentation level + +@item +never mix tabs and spaces (for indentation) + +@item +Code indented with a mixture of tabs and spaces should be +converted to using spaces exclusively + +Once this is done, we should add @code{python -tt} to the build +system to avoid such errors in the future. + +@end itemize + +There should be absolutely no tab characters for indentation in +any @code{.py} file in lilypond git. All such files should be +converted to use spaces only. + @node Grand LilyPond Input Syntax Standardization (GLISS) -- 2.39.2