-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
typing.Pattern not treated as a type #3537
Comments
Thank you for the issue, I can reproduce this with the latest pylint. |
Same with |
Totally agreed. IMHO most (any?) types/protocols from Btw. this seems to be duplicate of #3507 and probably #2287 as well as #1162 (see discussions in them as there is also the idea to "copy" the implementation |
Same with Callable |
This issue seems to be fixed when testing with the latest pylint version. |
The following code:
produces the following output:
Clearly, there's some problem with checking
Pattern
, as, for example,isinstance({}, Mapping)
produces no warning.The text was updated successfully, but these errors were encountered: