-
Notifications
You must be signed in to change notification settings - Fork 157
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
Dev: Cleanup and pep8 #213
Dev: Cleanup and pep8 #213
Conversation
Huh, I never knew of the pep8 standard of at least 2 spaces before an inline comment. |
Went through it all, there's only 2 things I'm not really a fan of that I marked above. Thanks! |
I was also surprised at the first time i read it. Among others. Personally i don't care if its 1, 2 or 3 but more or none spaces is imho counterproductive. BTW, fun fact: unrpyc code breaks NEARLY every line spacing rule: 😁 You have your own system with the code section comments e.g. # API or # Machinery so i don't touched this. I do not want to be a grammar nazi, but some rules make imho sense. At least to avoid chaos code. |
162e78f
to
4fc9c31
Compare
- membership should be tested with "(not) in"
- remove unused vars in exceptions - correct whitespace around operators, slices
- line break before keywords and operators - max-line-length formating - whitespace amount for inline comments - code stacking for better readability
4fc9c31
to
d7ad578
Compare
- wrong operator changes - adjust some format choices and line lengths
7f1d0e7
to
e8c1619
Compare
So, i made some changes according your comments. If you want other corrections just tell. It's no problem. |
TBH, those things are a bit too rigid at times. There's a lot I do agree with in general (empty lines after functions / classes etc) but sometimes you want to group some items together (or at least, separate them from some others clearly) and then things like too many empty lines between are just annoying. I think it's fine now, can you change it from a work in progress? |
The same. I like to do this for code parts but also imports. And then the formatter mucks it up.
Will do. I thought a draft brings some advantages but i noticed none. |
It just disallows me from merging it in the web UI. |
Not much in terms of code changes beyond removal of a few unused imports, vars, a leftover comment (init.py L489) and some added parens for code stacking. However a lot of formatting.