Skip to content
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

Closed
kmike opened this issue Dec 13, 2011 · 5 comments
Closed

Format code according to PEP 8 #6

kmike opened this issue Dec 13, 2011 · 5 comments

Comments

@kmike
Copy link

kmike commented Dec 13, 2011

There is no reason not to follow PEP 8 in 2011 :)

@fletom
Copy link

fletom commented Feb 13, 2012

Actually there is, at least in my opinion: PEP 8 really sucks.

@kmike
Copy link
Author

kmike commented Feb 13, 2012

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.

@kennethreitz
Copy link

Is someone really arguing against this?

@gxx
Copy link

gxx commented Oct 18, 2013

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.

@gruns
Copy link
Owner

gruns commented Oct 19, 2013

Merging with #18.

@gruns gruns closed this as completed Oct 19, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants