Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: Chris Angelico <rosuav@gmail.com>
Newsgroups: comp.lang.python
Subject: Re: Guido sees the light: PEP 8 updated
Date: Tue, 19 Apr 2016 23:41:06 +1000
Lines: 34
Message-ID: <mailman.13.1461073269.30862.python-list@python.org>
References: <5711c1b3$0$1596$c3e8da3$5496439d@news.astraweb.com> <dne6huFi9sfU1@mid.individual.net> <87shym6kpo.fsf@elektro.pacujo.net> <CAPTjJmrq-pFDGS14PE+FXx=B+fXBD-Pkqc9JdQrjULR9aXRSxg@mail.gmail.com> <mailman.43.1460795561.6324.python-list@python.org> <87h9f26ioa.fsf@elektro.pacujo.net> <1460809922.1918014.580580553.0AE05EE4@webmail.messagingengine.com> <CACwCsY5EG_RFHe8DMF4VStYCsSuO-gMC+KRx05q9=vu8aa3K9g@mail.gmail.com> <mailman.50.1460818461.6324.python-list@python.org> <878u0d7az5.fsf@elektro.pacujo.net> <CACwCsY5fLxQqG80POb=notQdC1T5crarf_aQ2VBkCT2fwZM-2Q@mail.gmail.com> <netsjl$quf$1@ger.gmane.org> <CAMB+yF0XcDSrPWPNYuwq7_99sas4eUoOJm7k-ymoFKDd85saow@mail.gmail.com> <mailman.151.1460986528.6324.python-list@python.org> <m18u0a1uxx.fsf@iKarel.lan> <86twix3mc5.fsf@rudin.co.uk> <87potlrfa1.fsf@elektro.pacujo.net> <20160419083101.5cdfe184@bigbox.christie.dr> <CAPTjJmqxY21Pq8SYqvXotYmd9v7MGw5oHbLu3K7ze4o3Ztmsag@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
In-Reply-To: <20160419083101.5cdfe184@bigbox.christie.dr>
Precedence: list
Xref: csiph.com comp.lang.python:107323

On Tue, Apr 19, 2016 at 11:31 PM, Tim Chase
<python.list@tim.thechases.com> wrote:
> Likewise, I detest aligning comments and almost always prefer to put
> them in a neighboring line if there's continuation:
>
>     foo = bar * 3 + 2 # we have 3 bars
>                       # plus one for margin on either side
>
> changing the length of the code portion (say, s/bar/inner_width/) will
> require re-indenting (and possibly re-flowing) the comments.
>
> It's even worse if the comment flows to an unrelated line
>
>     foo = bar * 3 + 2    # we have 3 bars
>     result = apply(bar)  # plus one for margin on either side
>
> Now, if either line of *code* changes, it requires rejiggering the
> comment indentation.
>
> If the comment gets moved above, it's no longer an issue:
>
>     # we have 3 bars plus one for margin on either side
>     foo = bar * 3 + 2
>     result = apply(bar)

Oh, absolutely! If the right-hand comment can't fit in the
right-hand-side, it needs to move above the code. The only time I'll
"wrap" that kind of comment is when it actually applies to both lines
of code:

width = bar * 3 + 2 # we have 3x2 bars, plus one...
height = bar * 2 + 2 # ... pixel of margin on all sides

ChrisA