This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients exhuma, ncoghlan, pmoody
Date 2014-03-01.13:00:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1393678807.87.0.335495199714.issue20815@psf.upfronthosting.co.za>
In-reply-to
Content
Unfortunately, the pep8 tool includes some additional invented rules of its own, mostly related to being far too strict about indentation of continuation lines.

PEP 8 is actually mostly silent on that topic, merely pointing out a couple of specific things *not* to do. It's the tool that extrapolates a whole host of continuation line indentation rules that even PEP 8 itself doesn't meet.

There's also no blanket requirement in the PEP to have spaces around all binary operators (since that doesn't always aid readability), just a limited subset of them.

I've recently filed a bug against the tool itself, suggesting that given its name, its default behaviour should be limited to things that are actually backed up by the PEP.

That said, I think some of the cases picked up here do represent genuine readability improvements due to improved alignment. They just need to be separated out from the spurious changes resulting from invented rules in the pep8 tool.
History
Date User Action Args
2014-03-01 13:00:07ncoghlansetrecipients: + ncoghlan, pmoody, exhuma
2014-03-01 13:00:07ncoghlansetmessageid: <1393678807.87.0.335495199714.issue20815@psf.upfronthosting.co.za>
2014-03-01 13:00:07ncoghlanlinkissue20815 messages
2014-03-01 13:00:07ncoghlancreate