-
-
Notifications
You must be signed in to change notification settings - Fork 695
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
Make Flake8 line limit consistent with Black and shorten lines to comply #2993
Conversation
341380c
to
ab46261
Compare
This makes it consistent with the limit set in Black.
ba1b65e
to
4308d0e
Compare
65140d7
to
c99058f
Compare
Those CI failures are mine - I'll get them fixed. |
Please do not use a force push to alter commits which have already been reviewed, as it breaks the "Show changes since your last review" feature in GitHub. If you need to bring in changes from the main branch, you can use a merge rather than a rebase. |
There's no consistency in the line lengths of the comments. For example:
To avoid unnecessary noise and merge conflicts, I think we should do the following:
Previous discussion: #2956 (comment) |
Agreed about the general guidelines - but:
There's only 1 change in this file, and it's because the first line is 89 chars. The new flow ends up with the second line being 88 chars. Have I misunderstood what you're referring to?
Agreed.... but that's what we want, right? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, you're right – I must have lost the indentation when I copied the line into an editor to measure it.
Yes, I was just using it as a comparison. |
Flake8 line limit is inconsistent with Black, this PR updates the config to be consistent, and shortens lines to comply with the new limit, as required.
Some lines with very long method names were skipped, ironically by making them even longer and adding a noqa comment
Fixes #2975
PR Checklist: