Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path: <torriem+gmail@torriefamily.org>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.003
X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'programmer': 0.03; 'languages,': 0.04; 'subject:Python': 0.06; 'strict': 0.07; 'suppose': 0.07; 'forcing': 0.09; 'sure,': 0.09; 'changes': 0.15; 'braces': 0.16; 'exist.': 0.16; 'from:addr:torriem': 0.16; 'from:name:michael torrie': 0.16; 'indent': 0.16; 'too).': 0.16; 'wrote:': 0.18; 'all,': 0.19; 'bit': 0.19; 'coding': 0.22; 'header :User-Agent:1': 0.23; 'stick': 0.24; 'fairly': 0.24; 'regardless': 0.24; '(or': 0.24; 'header:In-Reply-To:1': 0.27; 'am,': 0.29; 'asked': 0.31; 'code': 0.31; 'easier': 0.31; '(although': 0.31; 'continually': 0.31; 'idea,': 0.31; 'trivial': 0.31; 'probably': 0.32; 'run': 0.32; 'worked': 0.33; 'programmers': 0.33; 'style': 0.33; 'maybe': 0.34; 'but': 0.35; 'subject:?': 0.36; 'should': 0.36; 'employee': 0.37; 'wrong': 0.37; 'too': 0.37; 'being': 0.38; 'message-id:@gmail.com': 0.38; 'to:addr:python-list': 0.38; 'rather': 0.38; 'that,': 0.38; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'first': 0.61; 'such': 0.63; 'more': 0.64; 'world': 0.66; 'subject: & ': 0.68; 'guides': 0.74; 'lazy': 0.91
X-Virus-Scanned: amavisd-new at torriefamily.org
Date: Sat, 06 Dec 2014 10:29:12 -0700
From: Michael Torrie <torriem@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131118 Thunderbird/17.0.11
MIME-Version: 1.0
To: python <python-list@python.org>
Subject: Re: Tabs for indentation & Spaces for alignment in Python 3?
References: <CAFaCOgzqxcvuKBrcSkK+DRm-5pHuh6QCXi1PKG4LHGqdBjLF_A@mail.gmail.com> <m5tpqg$iqi$1@ger.gmane.org> <54827250.5060907@gmail.com> <dab9ca01-6f52-4186-8576-d295cdccbd90@email.android.com>
In-Reply-To: <dab9ca01-6f52-4186-8576-d295cdccbd90@email.android.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list/>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.16657.1417886958.18130.python-list@python.org>
Lines: 22
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1417886958 news.xs4all.nl 2897 [2001:888:2000:d::a6]:49629
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:82044

On 12/06/2014 10:12 AM, Simon Ward wrote:

> Not every programmer is as conscientious in the first of place, and
> that's far easier to get wrong than just agreeing to stick to one
> thing. This is why (often more rigid) style guides (or rather
> policies) exist.

Sure, but in the world of braces languages, reformatting crappy code is
fairly trivial

> Maybe we should sack such programmers regardless of their other
> abilities instead of forcing all, including the conscientious,
> programmers to adhere to strict style policies? While I like the
> idea, I think that a slap on the wrist and a bit of
> re-indentation/re-alignment is all that is necessary (although I have
> worked with people who consider pure style changes to be a sin too).

I suppose if an employee continually submits commits that violate the
coding standard after being asked time and again to not do that, and is
too lazy to run his code through GNU indent probably should be fired.