Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The pep8 standard is also an easy read with so many useful explanations:

https://www.python.org/dev/peps/pep-0008/



Don't let it turn you into a fucking pedant, though.


When it comes to maintaining standards in a code base, one needs to be a pedant.


The mentality of someone who thinks that an 89-character line that ends with " # noqa" is better than the 81-character line without that ending because now it passes flake8 is one I'll never understand.


Never seen someone do that. That's pretty bad.

I was more defending being a pedant about whatever coding standards your team agrees upon rather than any specific PEP-8 standard.

It is no problem to increase PyLint's line length limit if your team wants to use something other than the PEP-8 79 character limit.


I don't disagree, but keep in mind that on the large codebase you want to avoid false negative in term of pep8 errors.. I.e. if every time you build you see 100s of errors, you start to ignore those.


+1 to that.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: