We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Bug Report
(A clear and concise description of what the bug is.)
To Reproduce
The following code reproduces the issue
from typing import List class Foo(): def __init__(self): pass def test_make_update_sql_multiple(): where_args: List[Foo] = {"any": "thing"} print(where_args)
Expected Behavior
The following code produces the expected behavior (raise an error with assigning a dict to a List)
from typing import List class Foo(): def __init__(self): pass where_args: List[Foo] = {"any": "thing"} print(where_args)
Actual Behavior
Mypy sees no problem
Your Environment
mypy.ini
The text was updated successfully, but these errors were encountered:
https://mypy.readthedocs.io/en/stable/common_issues.html#no-errors-reported-for-obviously-wrong-code
Sorry, something went wrong.
Has there been any thought of enabling "--check-untyped-defs" by default? Someone seems to trip on this at least once a week.
Yes, I agree the current behavior is not at all intuitive. #11201 lists it as a possible change.
No branches or pull requests
Bug Report
(A clear and concise description of what the bug is.)
To Reproduce
The following code reproduces the issue
Expected Behavior
The following code produces the expected behavior (raise an error with assigning a dict to a List)
Actual Behavior
Mypy sees no problem
Your Environment
mypy.ini
(and other config files): N/AThe text was updated successfully, but these errors were encountered: