Re: the war on trailing whitespace

From: Andreas Ericsson <ae@op5.se>
Date: Feb 27, 2006, 11:41 UTC
Message-ID: <4402E56D.4010606@op5.se>
In-Reply-To: <94fc236b0602270326s3079d737l102d5728d59f0c98@mail.gmail.com>

Adrien Beau wrote:

Show 17 quoted lines

> On 2/27/06, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> 
>>there is a good reason not to enable the no-whitespace-at-eol checking in
>>pre-commit by default (at least for *all* files) for git development:
>>
>>        Python.
>>
>>Just do a "/ $" in git-merge-recursive.py. These whitespaces are not an
>>error, but a syntactic *requirement*.
> 
> 
> No, they aren't.
> 
> A logical line that contains only spaces and tabs is ignored by
> Python. (All the "dirty" lines in git-merge-recursive.py are such
> lines.)
>

I think the question is whether completely empty lines are also ignored by Python, or if they start a new block of code. Whatever the case, it must hold true for both 2.3 and 2.4.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231