Disable pylint 1.6 warnings / work around breakage #1974
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
googlebot
added
the
cla: yes
|
Should we set the pylint version back to 1.5.6? |
|
AFAIK this PR should make pylint 1.6 work fine for us. |
|
Yeah it did, and I see that pylint-dev/pylint#998 is getting jumped on pretty quick. Never mind then :) |
This was referenced Aug 3, 2016
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Work around pylint-dev/pylint#998
Globally disable new warnings (rather than just for tests, as in #1967).
Run pylint a single file at a time: if any exits with a non-zero status, record the name and status and continue (this helped debug the issue above).