Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork3k
Open
Description
I've confirmed the following works in pyright and pyrefly - but not in mypy:
fromdataclassesimportdataclassfromtyping_extensionsimport (Awaitable,Callable,Generic,TypeVar,assert_type,)T=TypeVar("T")@dataclassclassAgent(Generic[T]):output_type:Callable[...,T]|Callable[...,Awaitable[T]]asyncdefcoro()->bool:returnTruedeffunc()->int:return1# worksassert_type(Agent(func),Agent[int])# mypy - error: Argument 1 to "Agent" has incompatible type "Callable[[], Coroutine[Any, Any, bool]]"; expected "Callable[..., Never] | Callable[..., Awaitable[Never]]" [arg-type]coro_agent=Agent(coro)# pyright, pyrefly - works# mypy - error: Expression is of type "Agent[Any]", not "Agent[bool]"assert_type(coro_agent,Agent[bool])# worksassert_type(Agent[bool](coro),Agent[bool])
I wantT
to be inferred as the ultimate return type of the awaitable if an async function is passed rather than a regular one, but I suppose it's ambiguous which side of the union is the best match.
It would be great to see this work in mypy, but I'm also open to suggestions to do this in a less ambiguous way!
- This is related to a new PydanticAI feature, if you're curious check outSupport functions as output_type, as well as lists of functions and other types pydantic/pydantic-ai#1785 (comment)