-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Fix crashes with unpacking SyntaxError #11499
Conversation
In general, mypy doesn't promise to be able to check the remainder of your code in the presence of syntax errors, so just make this a blocking error. Fixes python#9137 Fixes python#3825 (most of the reports in this issue were fixed by python#8827)
This comment has been minimized.
This comment has been minimized.
@hauntsaninja Is it okay if a new mypy contributor finishes this PR as an onboarding task? |
Yeah of course! Although a blocking error on aiohttp is not an acceptable regression. |
@JukkaL What is the situation with this? It has been almost three months without news, maybe it would be better let @hauntsaninja actually finish this? I would prefer to get this into 1.0 |
According to mypy_primer, this change has no effect on the checked open source code. 🤖🎉 |
Cool, got this working. Assuming we're okay with potential new blocking errors this could be merged |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW syntax errors should be blocking, so I think this is good. Of course we need to be sure we marked all possible locations as valid.
In general, mypy doesn't promise to be able to check the remainder of
your code in the presence of syntax errors, so just make this a blocking
error.
Fixes #9137
Fixes #3825 (most of the reports in this issue were fixed by #8827)