-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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 pylint clean-up. #1780
Small pylint clean-up. #1780
Conversation
I'd be in favor of globally disabling |
Good point. 100% code coverage makes all true import failures abundantly clear. |
@tseaver PTAL |
@@ -87,6 +87,10 @@ load-plugins=pylint.extensions.check_docs | |||
# """Hi everyone""" | |||
# and thus causes subsequent imports to be | |||
# diagnosed as out-of-order. | |||
# - wrong-import-position: This error is overzealous. It assumes imports are |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
OK @tseaver I got rid of the erroneous line. Is this good to merge (after squashing)? |
LGTM |
- Increasing test lines limit to 1900 and removing a line limit ignore at the top of the file - Disabling no-name-in-module since requiring 100% code coverage guarantees we exercise all imports - Making remaining disables use verbose names instead of short names - Locally re-enabling too-many-statements in gcloud/bigquery/test_table.py (was disabled at a scope but never re-enabled)
bfd32e7
to
0352542
Compare
gcloud/bigquery/test_table.py
(was disabled at a scope but never re-enabled)@tseaver This was inspired by #1779 (e.g. my comment made me wonder about this)