On Mon, Jul 19, 2021 at 12:16 AM Matthew Rahtz via Typing-sig <typing-sig@python.org> wrote:
[Alfonso]
> I wonder if you could give more concrete examples about what other behaviors could bound=... have apart from what we have commented

The specific thing I was thinking of is, are there going to be any situations where we'd use a TypeVarTuple but in practice always pass in, say, exactly 4 types? In cases like that one might want set, say, bound=Tuple[int, str, str, float]. Admittedly now that I say this out loud this seems like a perverse use-case - why wouldn't you just use normal TypeVars in that case? - but maybe there could be situations where it would be more convenient somehow to use a TypeVarTuple...?

A use case might involve constructing other types using the * operator. That doesn't work with TypeVar, only with TypeVarTuple.

--
--Guido van Rossum (python.org/~guido)