On Sat, Apr 16, 2016 at 8:32 AM, Stephen Hansen <me+pyt...@ixokai.io> wrote: > On Sat, Apr 16, 2016, at 01:51 AM, Marko Rauhamaa wrote: >> Chris Angelico <ros...@gmail.com>: >> >> > On Sat, Apr 16, 2016 at 6:06 PM, Marko Rauhamaa <ma...@pacujo.net> wrote: >> >> It doesn't really matter one way or another. The true WTF is that it's >> >> been changed. >> > >> > Why? Was PEP 8 inscribed on stone tablets carried down from a mountain? >> >> In a way, yes. >> >> I don't follow PEP 8 to the tee; probably nobody does. However, I don't >> see the point of turning truckloads of exemplary Python code into >> truckloads of substandard Python code. > > This attitude is part of the problem: not following PEP8 does not make > code "substandard". PEP8 was never meant to be an authoritative metric > of 'good'. Its a set of guidelines that are subject to change over time > (this isn't even KINDA the first change!) and represent the core devs > taste and particular needs, and it goes out of its way to say that it is > only a suggestion and other concerns (especially local consistency) > override its advice.
I have worked for many companies where you are required to get a clean run of pep8 on your code before your pull request will even be considered for approval. I don't agree with this at all, as I think it makes the code very ugly, especially enforcing the max line length. I have referred people to this, but it fell on blind eyes: https://www.python.org/dev/peps/pep-0008/#a-foolish-consistency-is-the-hobgoblin-of-little-minds -- https://mail.python.org/mailman/listinfo/python-list
