Fix no-member
in type annotations with future import
#6608
Merged
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
Don't emit
no-member
inside type annotations withfrom __future__ import annotations
.With PEP 563, annotations are stored as strings and thus not executed. This can cause false-positives if attributes are used which don't exist in the version used to run pylint.
If Python 3.8 is used, pylint would currently emit a
no-member
error forast.Match
(which was added in3.10
).By excluding type annotations with
from __future__ import annotations
, the behavior will be similar to normal string annotations (which don't emit an error).Closes #6594