Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Error when using tuple base class not detected #867

Closed
JukkaL opened this issue Sep 2, 2015 · 0 comments · Fixed by #3952
Closed

Error when using tuple base class not detected #867

JukkaL opened this issue Sep 2, 2015 · 0 comments · Fixed by #3952
Labels
bug mypy got something wrong

Comments

@JukkaL
Copy link
Collaborator

JukkaL commented Sep 2, 2015

Assume m.pyi like this:

from typing import Tuple
a = ... # type: A
class A(Tuple[int, str]): ...

Now this error isn't caught by mypy:

from m import a
a[0]()

This is caused by the class definition being after the type reference in m.pyi. Apparently tuple item types don't get propagated because the class hasn't been semantically analyzed yet when binding the type.
@JukkaL JukkaL added the bug mypy got something wrong label Sep 2, 2015
@ilevkivskyi ilevkivskyi mentioned this issue Sep 13, 2017
Merged
JukkaL pushed a commit that referenced this issue Sep 27, 2017
@ilevkivskyi @JukkaL
Fix crashes and fails in forward references (#3952)
a611b11 
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug mypy got something wrong
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix crashes and fails in forward references ilevkivskyi/mypy
1 participant
@JukkaL