Repository navigation
NamedTuple with no fields causes "object" not callable error #1276
Description
Blue = NamedTuple("Blue", [])Fails with:
example.py:5: error: "object" not callableBut this code runs fine in python2/python3.
Edit:
Seems like it's falling out to here
a bit odd to me because NamedTuple does indeed have a __call__ attribute
Interesting. The following fails:
alist = [('afield', str)]
Green = NamedTuple("Green", alist)
example.py:3: error: List literal expected as the second argument to namedtuple()
example.py:3: error: "object" not callableBut this works:
Green = NamedTuple("Green", [('afields', str)])I think the type_map is storing NameExpr(NamedTuple [typing.NamedTuple]) as an object, and it looks like the in the latter case it's skipping a check . . . I remember reading in an issue that NamedTuple wasn't fully supported, so I assume that's what's going on.
Activity
gvanrossum commentedon Mar 6, 2016
I think I know what this is. Because there are no items, the code here thinks there's an error. It then skips the assignment to
call.analyzeda few lines later. Maybe it can be fixed by changing "return" to "info =" in the error branch.gvanrossum commentedon Mar 6, 2016
FWIW the thing you noted with using a variable for the list of fields is unrelated -- it's a general thing that mypy doesn't understand dynamically constructed types.