Right now all `Concatenate` tests do not cover `Callable[..., Concatenate]` case.

Link: https://github.com/python/cpython/blob/09087b8519316608b85131ee7455b664c00c38d2/Lib/test/test_typing.py#L4862-L4877

I think, that this should be improved. It is an important case.
PR is on its way.

Sorry I'm confused: Callable[..., Concatenate] is invalid usage. So I don't think we need to test it.

https://docs.python.org/3/library/typing.html#typing.Concatenate. "Concatenate is currently only valid when used as the first argument to a Callable."

> Sorry I'm confused: Callable[..., Concatenate] is invalid usage. So I don't think we need to test it.

Yes, my bad :)

In this case, do we need to make this a `TypeError`? Right now you can use `Concatenate` as the return type.

> In this case, do we need to make this a `TypeError`? Right now you can use `Concatenate` as the return type.

Last I recall, we stopped checking anything in the param args of Callable since 3.10 because it has too many problems with inter-version typing and typing_extensions usage. E.g. in Python 3.8

Callable[typing_extensions.Concatenate[...], ...]

was extremely difficult to implement in typing_extensions since Callable checks were too strict back then (they only allowed list of args). So to avoid such problems in the future, we ceased all param args checking.

For the return arg, I'm not too keen on adding more checks for the same reason of allowing future additions. Also the static type checker should warn the user and mypy correctly does that.

Thank you for the explanation, Ken Jin.

Going to close this issue as invalid.