This check is potentially problematic because it could force evaluation of
annotations unnecessarily. This doesn't trigger for builtin objects (functions,
classes, or modules) with annotations, but it could trigger for third-party objects.

The check was not particularly useful anyway, because it succeeds if__annotations__
is a dict or None, so the only thing this did was guard against objects that have an
__annotations__ attribute that is of some other type. That doesn't seem particularly
useful, so I just removed the check.
(cherry picked from commitcb6596c)

Co-authored-by: Jelle Zijlstrajelle.zijlstra@gmail.com

Issue:Avoid eagerly evaluating annotations #132493

pythongh-132493: Remove __annotations__ usage in inspect._signature_i…

775435e

…s_functionlike (pythonGH-133415)This check is potentially problematic because it could force evaluation ofannotations unnecessarily. This doesn't trigger for builtin objects (functions,classes, or modules) with annotations, but it could trigger for third-party objects.The check was not particularly useful anyway, because it succeeds if ``__annotations__``is a dict or None, so the only thing this did was guard against objects that have an``__annotations__`` attribute that is of some other type. That doesn't seem particularlyuseful, so I just removed the check.(cherry picked from commitcb6596c)Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>

This was referencedMay 10, 2025

Avoid eagerly evaluating annotations#132493

Open

gh-132493: Remove __annotations__ usage in inspect._signature_is_functionlike#133415

Merged