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.

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

Inconsistent representations for named tuples #3016

Closed
JukkaL opened this issue Mar 16, 2017 · 0 comments · Fixed by #3952
Closed

Inconsistent representations for named tuples #3016

JukkaL opened this issue Mar 16, 2017 · 0 comments · Fixed by #3952

Comments

@JukkaL
Copy link
Collaborator

JukkaL commented Mar 16, 2017

I have these two modules that form an import cycle:

# a.py
from collections import namedtuple
from b import f

N = namedtuple('N', 'a')

class X(N):
    pass
# b.py
import a

def f(x: a.X) -> None:
    reveal_type(x) # a.X
    y = a.X(1)
    reveal_type(y) # Tuple[Any, fallback=a.X]

The revealed types for two values with the same type a.X differ depending on how the type was constructed (see the comments above). The explanation is that when mypy processes the type annotation of f, is doesn't yet know that it is a named tuple type. The type of a.X(1) is determined later during type checking, and mypy then knows that it's a named tuple.

Not sure what's the best way to fix this. We could perhaps fix up named tuple types in the third pass of semantic analysis when this knowledge is available.

JukkaL pushed a commit that referenced this issue Sep 27, 2017
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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants