Re: the war on trailing whitespace

From: Adrien Beau <adrienbeau@gmail.com>
Date: Feb 27, 2006, 11:26 UTC
Message-ID: <94fc236b0602270326s3079d737l102d5728d59f0c98@mail.gmail.com>
In-Reply-To: <Pine.LNX.4.63.0602271004130.5937@wbgn013.biozentrum.uni-wuerzburg.de>

On 2/27/06, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 8 quoted lines

>
> 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.)

Besides, spaces, tabs and newlines can be used interchangeably to separate tokens, so trailing whitespace is never *required*.

Hope this helps,

Adrien