News for hackers. Stuff that matters.
Re:Python coding standards by mapleoin on Monday September 16, 2013 @09:01AM (#6393004)
This article makes no mention of flake8: http://flake8.readthedocs.org/en/2.0/

which is the up-to-date python style checker built on top of pep8 and pyflakes.

Re:Python coding standards by etfb on Monday September 16, 2013 @09:25AM (#6393089)
Some of the stuff in PEP8 is pretty subjective. What's the state of play for fixing that with an automated tool? Does is spit out advisories, or has some effort been put into the Small Matter Of Programming of interpreting the intent of code? I presume nothing can be done about

    x += 1    # increment x
Re:Python coding standards by herge on Monday September 16, 2013 @10:03AM (#6393279)
You can pass flags to pep8 to ignore specific errors. For our project, we have:

--max-line-lenght=120 --ignore=E128

Re:Python coding standards by kvalle on Monday September 16, 2013 @09:26AM (#6393091)
Came to say the same. A call to flake8 is a very useful step in most of my Git pre-committ hooks.