-
Notifications
You must be signed in to change notification settings - Fork 955
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
PEP8 style guide #78
Comments
The original author didn't (for whatever reason he had) and when I merged On Wed, Jul 3, 2013 at 11:34 PM, Daniil notifications@github.com wrote:
Bear bear@xmpp.org (email) PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29 |
PEP8 styled code looks more familiar for many python developers (especially that ones who uses IDE with automatic style correctors). BTW 4 spaces per indentation levels looks way better as I think. So PEP8 code will be more comfortable to contribute to. |
The question of 2 spaces or 4 is irrelevant - all modern IDE's and editors The question of comfortable code is also not a primary reason - this The better way to approach this issue would have been to submit the pull I have had this discussion (and many variants of it) more times than I can Post v1.0 release was going to be the time when I started asking questions On Thu, Jul 4, 2013 at 1:46 AM, Daniil notifications@github.com wrote:
Bear bear@xmpp.org (email) PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29 |
I'm kinda new here and don't have experience of collaboration with other developers at all. Sorry for my mistakes with that. |
I came across more grumpy than I wanted - sorry about that. I was trying to say that "yes we can talk about it, but not in the context Actually it is a big issue if, and let me know if I get this wrong, that So yes, please do start another thread and let's close this one with a thanks! On Thu, Jul 4, 2013 at 2:19 AM, Daniil notifications@github.com wrote:
Bear bear@xmpp.org (email) PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29 |
What I would like to suggest is that you create a pep8 branch in your fork and then make the changes so we can test how it works and if it breaks anything. I was thinking about this just now and your idea is great and it may even help the Python 3 branch - so please do consider doing this. |
For some reason I thought I was responding to you in the mailing list - that's why I said "close the thread". Only just now realized it was an Issue we were talking in :) |
Ok. I thought I should open pull request in order to continue discussion on this topic :)
Yep! I created one in my fork. Working on it. |
that would work also - cool (I just got worried that my being in a grumpy cranky-old-man mood might On Thu, Jul 4, 2013 at 3:03 AM, Daniil notifications@github.com wrote:
Bear bear@xmpp.org (email) PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29 |
Okay, I see you've got it sorted out already. ;) For what it's worth: I find that PEP8 in general is a good idea and most IDEs (and even vim) can enable a PEP8 style-checker. So it would help the code to stay uniform and clean. The question is, how to integrate this without too much work. We still have a lot of clean-up to do that potentially could remove thousands of lines of code and to rewrite this code according to PEP8 beforehand seems like a waste of time... |
Why don't you use PEP8 style guides?
http://www.python.org/dev/peps/pep-0008/
The text was updated successfully, but these errors were encountered: