Object in localns but signature of inner function not resolved about in-n-out HOT 4 CLOSED

Thinking about it more, of course it wouldn't work, the outer function is defined but never called until runtime

from in-n-out.

Actually I would not expect that to resolve. You've hit on one of the big issues in usage of type annotations at runtime.

This is a long and complicated topic with lots written elsewhere, so I'll just link to relevant peps and you should search them:

• https://lukasz.langa.pl/61df599c-d9d8-4938-868b-36b67fdb4448/ (see the section "where pep 649 helps")
• https://peps.python.org/pep-0563/
• https://peps.python.org/pep-0649/

Long story short, that usage just won't be supported. You would need to not use __future__.annotations or import at the global level

from in-n-out.

You can also read through pydantic/pydantic#2678

Point is, what we're trying to do here (using types at runtime) does have some limitations and caveats, and does kinda rely on a little "participation/cooperation" on the part of the end user, just as it does in pydantic

from in-n-out.

Okay interesting, thanks for the info, I'll close this!

from in-n-out.