-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Format code according to PEP 8 #6
Comments
Actually there is, at least in my opinion: PEP 8 really sucks. |
The real value of PEP 8 is not the conventions by themselves (4 spaces vs 2 spaces is not an important question and there are almost zero practical reasons to prefer one of the ways per se), its value is that these conventions are followed by the whole python community so python developers have 1 less obstacle with somebody else's source code. |
Is someone really arguing against this? |
can't believe in two years this hasn't been pep8'd. forked the repo and did it in 5 minutes, it's that easy. |
Merging with #18. |
There is no reason not to follow PEP 8 in 2011 :)
The text was updated successfully, but these errors were encountered: