Hacker News new | ask | show | jobs
by leephillips 3133 days ago
From the PEP8 style guide:

"Many projects have their own coding style guidelines. In the event of any conflicts, such project-specific guides take precedence for that project."

and

"A Foolish Consistency is the Hobgoblin of Little Minds".

And, throughout, PEP8 makes it clear that it is a set of recommendations, and that if a project or community already has an established style, it need not be changed.

2 comments

You misunderstand. I’m not criticizing Google not following PEP8. They’re welcome to make whatever modifications they want. I do the same. For example, I don’t like having two blank lines between methods and I don’t limit my line widths to 80 characters. This personal or project level alteration is fine. However, when your target audience is the Python community at large, you are better off following the PEP8 standard, which everyone knows and is comfortable with, rather that a project specific format, just because you personally find it more convenient. Standards are pretty important in the publishing industry, so I’m not sure why this is so controversial here today.
Why are you arguing against PEP8? As you mentioned in your final sentence, the Python community DOES have an established standard. It is called PEP8. The parent has made a valid point. Why would you criticize or trash his "karma" for stating it?
You say I'm arguing against PEP8 by quoting PEP8? That's hard to understand. Whose karma am I "trashing", and how? I certainly didn't downvote him, if that's what you mean.