You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tolerate lazily-evaluated type aliases in the input_required return check
Accessing `__value__` on a PEP 695 `type X = ...` alias evaluates it, so an
alias naming TYPE_CHECKING-only imports raised NameError at registration for
resolver-using tools that registered fine before the check existed. Such an
alias declares no arm the check can see; the in-call guard still covers a
body that returns an InputRequiredResult.
Also pin the neighboring shapes that already work: a subscripted generic
alias forwards `__value__` to its origin and is rejected, and a
parameterized builtin generic return registers on every supported Python.
0 commit comments