-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Crash with forward reference in NamedTuple #3315
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
Comments
Reverting #3305 fixes it (cc @ilevkivskyi). |
Thanks for testing! We should get to this one way or another before the release. @JukkaL. |
My PR surfaced the bug already present in |
OK, I have fixed these two crashes and also three crashes from #3308 (for both class and functional syntax, total nine crash scenarios). I will now add tests and make a PR. The point is that "synthetic" types were sometimes ignored in the third pass, now they are correctly processed. |
I'm working on a quick fix that just uses |
Created a separate issue for the TypedDict crash so that these can be tracked independently (#3319). |
Found this testing my production codebase against mypy master:
Haven't tried yet to minimize this further. Hopefully we can get this fixed before the release.
Edit: this also repros with TypedDict:
The text was updated successfully, but these errors were encountered: