-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
INTERNAL ERROR: 'NoneType' object is not iterable #3836
Comments
Could you please provide the code that causes this? But from the traceback it looks related to #3799 (maybe a duplicate). |
I found a small repro:
|
Perhaps related, it looks like the resolution of the string type hint 'MyNamedTuple' is happening too late, or is incorrect? This code:
produces
|
Then it looks very similar to the crashes reported in #3419 (not sure if it is a duplicate). In general, forward references (string type hints) to "synthetic" types is a known problem. I hope it will be fixed very soon. |
Confirmed that a version with forward references, but not based on namedtuple, but rather "private" fields (leading underscore) and @Property getters (but not setters) works fine. Thanks! More verbose, but a fine work around until recursive NamedTuples are supported better. |
Forward references didn't work with anything apart from classes, for example this didn't work: ``` x: A A = NamedTuple('A', [('x', int)]) ``` The same situation was with `TypedDict`, `NewType`, and type aliases. The root problem is that these synthetic types are neither detected in first pass, nor fixed in third pass. In certain cases this can lead to crashes (first six issues below are various crash scenarios). This fixes these crashes by applying some additional patches after third pass. Here is the summary of the PR: * New simple wrapper type `ForwardRef` with only one field `link` is introduced (with updates to type visitors) * When an unknown type is found in second pass, the corresponding `UnboundType` is wrapped in `ForwardRef`, it is given a "second chance" in third pass. * After third pass I record the "suspicious" nodes, where forward references and synthetic types have been encountered and append patches (callbacks) to fix them after third pass. Patches use the new visitor `TypeReplacer` (which is the core of this PR). Fixes #3340 Fixes #3419 Fixes #3674 Fixes #3685 Fixes #3799 Fixes #3836 Fixes #3881 Fixes #867 Fixes #2241 Fixes #2399 Fixes #1701 Fixes #3016 Fixes #3054 Fixes #2762 Fixes #3575 Fixes #3990
The text was updated successfully, but these errors were encountered: