-
Notifications
You must be signed in to change notification settings - Fork 30
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
Convert to using the PEP 8 style guide #16
Comments
@Nihilate: I'm happy to take this one if you want to assign it to me. I think it'll help make the other issues in this project a little easier to tackle. |
Sounds good to me, go ahead :) |
FWIW, I think that once the majority of PEP8 violations are taken care of then linting should be added as a CI step to keep the code from regressing in that regard. |
Hey, @Nihilate, I did some work on this last year, but since then I've come to really enjoy using Black to just auto-format code. Would you be amenable to closing this issue in favor of resolving all style issues through auto-formatting? I'd be happy to open an issue and submit a corresponding PR if that sounds good to you. |
Hey! Sounds reasonable to me - I've been using RuboCop at work and the auto-formatter for that has been really useful. I'll open another issue. |
I've created a new enhancement over here: #73 |
All files, functions and variables should follow the recommended Python style guide (PEP 8).
The text was updated successfully, but these errors were encountered: