Path: csiph.com!news.swapon.de!fu-berlin.de!uni-berlin.de!not-for-mail
From: Ben Finney <ben+python@benfinney.id.au>
Newsgroups: comp.lang.python
Subject: Falsehoods People Believe about PEP 8 (was: Guido sees the light: PEP 8 updated)
Date: Sun, 17 Apr 2016 06:21:54 +1000
Lines: 56
Message-ID: <mailman.61.1460838131.6324.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> <CAPTjJmpxiYh=yKosufJvEvm5sOqeSTbgBHWCY4jFq-gmDeTa=Q@mail.gmail.com> <85potpuwwt.fsf_-_@benfinney.id.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Cancel-Lock: sha1:xkCfqlv3A2yuin6UQmYquwPE6ls=
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux)
Precedence: list
Xref: csiph.com comp.lang.python:107111

Chris Angelico <rosuav@gmail.com> writes:

> Maybe we need a blog post "Falsehoods Programmers Believe About PEP
> 8", along the lines of the ones about time and names.

Great suggestion. (Do you have a blog on which you could post an article
like this?)

> Remember, every one of these is false.
>
> * All Python code should follow PEP 8.
>
> * If you use a tool named pep8, your code will be PEP 8 compliant.
>
> * If your code is PEP 8 compliant, a tool named pep8 will accept it.
>
> * The Python Standard Library is PEP 8 compliant.
>
> * Okay, at least the new parts of the standard library are PEP 8
>   compliant.
>
> * PEP 8 compliant code is inherently better than non-compliant code.
>
> * PEP8-ing existing code will improve it.
>
> * Once code is PEP 8 compliant, it can easily be kept that way through
>   subsequent edits.
>
> * PEP 8 never changes.
>
> * Well, it never materially changes.
>
> * I mean, new advice, sure, but it'll never actually go back on a
>   rule.

* The line length limit is obsolete in an age of high-resolution
  displays.

* Okay, but if you disregard side-by-side windows, lines of code can be
  arbitrarily long without hurting readability.

* Well, maybe not several hundred characters, but surely 120 characters
  of code on a line is easy enough to read.

* The only valid white space is line breaks and U+0020 SPACE.

* Okay, U+0009 TAB when lining up columns, but no other white space.

* Oh, come on, no-one would use U+000C FORM FEED in source code.

-- 
 \       “The apparent lesson of the Inquisition is that insistence on |
  `\         uniformity of belief is fatal to intellectual, moral, and |
_o__)    spiritual health.” —_The Uses Of The Past_, Herbert J. Muller |
Ben Finney