[issue46571] Strange `@typing.no_type_check` behavior for class variables

[Jelle Zijlstra]

Jelle Zijlstra <jelle.zijlstra at gmail.com> added the comment:

Let's not jump into deprecating it.

I think (2) makes the most sense. If we can get that working reliably (using __qualname__ I assume), it would be my preference; otherwise we should do (1).

This problem can also affect function objects, right? `class B: meth = some_function`.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue46571>
_______________________________________