Fix pylint legacy warnings #950
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
Pierre-Sassoulas
force-pushed
the
fix-pylint-legacy-warnings
branch
from
030830e
to
4804d71
Compare
Pierre-Sassoulas
force-pushed
the
fix-pylint-legacy-warnings
branch
from
4804d71
to
4fedab7
Compare
Pierre-Sassoulas
force-pushed
the
fix-pylint-legacy-warnings
branch
from
4fedab7
to
b86bdf1
Compare
This was referenced Apr 19, 2021
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.
Description
There was no
__init__.pyin astroid/brain, so some problem were not detected. This prevented adding pre-commit for easy checking and also was a problem for packaging because we need to use find and not finenamespace for python 3.6.Type of Changes
Related Issue
#937 #947