-
-
Notifications
You must be signed in to change notification settings - Fork 740
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
small flake8 changes #318
small flake8 changes #318
Conversation
line length comes from @tw - i would prefer 80 columns personnally, but don't want to argue over that bikeshed the 120 limit *does* trigger warnings right now, but it's better to do that than to make the problem worse for future PRs
the initial configuration might have been in a way so stuff that is not fixed yet (but present) does not fail all the time, so only new issues are discovered. one can then remove exlusions when fixing the corresponding issues without having it to do all at once (or having it fail all over the place all the time). |
did you notice the travis failure? |
i did not notice the test failure, i'll take a look. the initial configuration was indeed a way to get flake8 working without too many warnings, but it seems it was too enthusiastic at censoring errors, at least from my perspective... 120 errors is certainly managable, especially since half of those are line length... |
tests should pass now. |
Current coverage is
|
followup for #4: we configure flake8 to be a little more strict so that new contributions are cleaner. i also fix errors i introduced in recent pull requests, to try to play catchup at least with the new stuff i submitted.
finally, i added a blurb to the development docs about flake8, because i had forgotten about it...
before this PR:
(and in the above, i deliberately skipped recursing into
.tox
, which it does by default now, which triples everything. this PR also fixes that.)after this PR:
about 30 of those are fixed in #316 as well.