Pyright: PEP 585 tuple cannot be parametrised like typing.Tuple

[layday]

Describe the bug
The built-in tuple type cannot be parametrised using the ellipsis or empty tuple and does not accept more than one argument, i.e. it behaves like a sequence.

To Reproduce
Type check the snippet below.

Expected behavior
That it should behave like typing.Tuple.

Screenshots or Code

from __future__ import annotations

# Variable length homogenous tuple:
#   Too many type arguments provided; expected 1 but received 2
#   "..." not allowed in this context
foo: tuple[str, ...] = ('a', 'b')   
# Empty tuple:
#   Expected class type but received "Tuple[()]"
bar: tuple[()] = ()
# Fixed length or heterogenous tuple:
#   Too many type arguments provided; expected 1 but received 2
fuz: tuple[str, str] = ('a', 'b')

VS Code extension or command-line
Extension, 1.1.69

[erictraut]

Thanks for filing this issue. This will be addressed in the next release of pyright.

[erictraut]

This is now addressed in Pyright 1.1.70, which I just published. It will also be in the next version of Pylance.

[layday]

Thanks for getting this in. I took the new version for a spin and I think tuples are not handled correctly when they're aliased:

Foo = Union['tuple[str, int]']

# Expression of type "Tuple[Literal[''], Literal[0]]" cannot be assigned to declared type "Foo"
#   TypeVar "_T_co" is covariant
#     Type "Literal['', 0]" cannot be assigned to type "str"
#       "Literal[0]" is incompatible with "str"
foo: Foo = ('', 0)


Bar = Tuple[str, int]

bar: Bar = ('', 0)  # All good

[erictraut]

Thanks. As you discovered, I missed one code path in my previous attempt to fix this. It will be fixed in the next release.

[erictraut]

This is now addressed in Pyright 1.1.71, which I just published.