Disabling warnings about members not existing by default #102
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
… can be turned on again in profiles with the member-warnings setting or the --member-warnings command line flag)
|
|
carlio
added a commit
that referenced
this pull request
Jan 31, 2015
Disabling warnings about members not existing by default
carlio
added a commit
to carlio/prospector
that referenced
this pull request
Jan 31, 2015
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.
The sad fact is that pylint's member warnings are wrong more often than they are right. As Prospector's aim is to reduce noise and make it really easy to get useful results, it seems pragmatic to simply turn those warnings off.
It can be turned on again in profiles with the member-warnings setting or the --member-warnings command line flag, but the default will now not include those warnings.