Pardon me if this is a naiive suggestion:
I'd like to suggest that the subversion property svn:eol-style of either
'native' or 'LF' be applied to all the files in this project.
I can see that wsgi_middleware.py has svn:eol-style of 'native'.
The purpose for doing this is to reduce the possibility of changes being
made due to silly line-ending problems.
What inspired this is a bunch of diff results from the version we're using
to the head revision that were invisible/whitespace changes.
This obviously can't be done by a patch :-)
$ find . -name '*.py' | xargs svn propset svn:eol-style 'native'
and then commit.
So, either this is on purpose that no files have an eol-style, or
wsgi_middleware has it by accident. I think it might be good to declare a
standard and go with it.
Or, I could be wrong, please feel free to opine.
Kevin J. Rice
Senior Software Engineer, Textura LLC
51-K Sherwood Terrace, Lake Bluff IL
(847) 235-8437 (spells VISAFLUIDS)
(847) 845-7423 (845-RICE, cellphone)
On Thu, Jul 26, 2007 at 01:39:15PM -0500, Kevin J. Rice wrote:
> So, either this is on purpose that no files have an eol-style, or
> wsgi_middleware has it by accident.
This was not on purpose. Probably the creator of wsgi_middleware.py
marked it by an accident or a habit from another project. Up until now we
haven't had a policy on line endings (most, if not all, developers are
I just removed the property from the file (and from 3 tests, BTW).
Committed in the revisions 2822-2825. If the "no policy" policy will cause
more harm than good I can rethink the policy and add the property to all
files (and svn:ignore *.py[co], too).
Oleg Broytmann http://phd.pp.ru/ phd@...
Programmers don't die, they just GOSUB without RETURN.