----- Original Message -----
> From: "Phil Harvey" <p...@philharveyonline.com>
> To: email@example.com
> Sent: Saturday, March 16, 2013 1:09:49 AM
> Subject: Re: Why 2 space indentations??
> I'm feeling a bit guilty about this one because I suspect it was my
> indentation-related review comments on some of Ken's recent soak test
> that may have been the catalyst for this thread.
Hi Phil - sorry bro, didn't mean to give you that impression. I've had issues
with this for awhile, it's just that the previous weekend I lost use of my
larger desktop monitor and had to struggle though using my tiny laptop screen
while writing that python code. By Monday, the fuse was lit.
My last comment on this (promise) - I'm fine with leaving the existing python
code at 2 space indent. Converting that to 4 and trying to manage
diffs/patches would probably be more frustrating than beneficial.
But going forward, new files should use 4 space indent to be consistent with
the existing C++ and Java QPID programming guidelines.
> We've got a few options about what to do, each bringing their own
> kind of pain.
> I would be in favour of converting existing Proton Python files to
> use 4
> spaces. This obviously entails the up-front pain of doing the
> plus some mild, occasional pain when diff-ing a file's version
> history that
> spans the re-indentation commit (you can ignore whitespace using "git
> --ignore-all-space" or "svn diff -x --ignore-space-change").
> I think this is preferable to the frequent, long-lasting pain of
> between 2-space and 4-space indentation when I navigate across files
> the project. Not to mention the occasional, *severe* pain of
> indentation styles on the mailing list. Surely no one is actually
> this discussion, and if we don't resolve it now then it's sure to
> come up
> again in six months time ;-)
> My second choice would be that we make all the Proton Python files
> 2-space indentation. Despite my preference, ceteris paribus, for 4
> this would be a less disruptive change based on Rafi's statistics.
> On 15 March 2013 12:15, Ted Ross <tr...@redhat.com> wrote:
> > +1. I've also wondered why this one codebase was written with
> > 2-space
> > indentation. My editors are all set up for 4-spaces so doing any
> > work in
> > this code is a pain.
> > I'm in favor of converting all of it to comply with the 4-space
> > convention.
> > -Ted
> > On 03/14/2013 09:18 AM, Ken Giusti wrote:
> >> Not to fire off a religious flame-war here - but this has stuck in
> >> my
> >> craw for awhile:
> >> Why is the proton C and Python code using 2 space indent?
> >> Two space indent does not conform with the existing QPID coding
> >> guidelines established for C++ nor Java:
> >> https://cwiki.apache.org/qpid/**java-coding-standards.html<https://cwiki.apache.org/qpid/java-coding-standards.html>
> >> https://cwiki.apache.org/qpid/**cppstyleguide.html<https://cwiki.apache.org/qpid/cppstyleguide.html>
> >> even python code should not be using 2 space indents, as God and
> >> Guido
> >> intended:
> >> http://www.python.org/dev/**peps/pep-0008/#indentation<http://www.python.org/dev/peps/pep-0008/#indentation>
> >> Heck - the proton-j Java code uses 4 spaces! We're not even
> >> self-consistent!
> >> Sorry to bring this up - there's plenty of real work that needs to
> >> be
> >> done for proton. But I'm OLD, and my eyes ain't what they used to
> >> be.
> >> Working with 2 space indents isn't fun. In the case of python,
> >> it's damn
> >> painful.
> >> Going forward, can we please use 4 space indents? And, over
> >> time,
> >> convert the existing codebase?
> >> -K