This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients AlexWaygood, JelleZijlstra, gvanrossum, kj, sobolevn
Date 2022-01-29.16:53:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
@no_type_check (introduced by PEP 484) is intended for static checkers, to signal to them that they shouldn't check the given function or class.

I don't think PEP 484 specifies its runtime effect -- arguably get_type_hints() could just ignore it. Or raise an exception when called on such a class. We could even argue that @no_type_check shouldn't have a runtime effect.

But before we change anything we should be guided by:

1. What is documented?
2. What does it do now?
3. How is that used by runtime type inspectors?
4. What would be most useful to runtime type inspectors?
Date User Action Args
2022-01-29 16:53:37gvanrossumsetrecipients: + gvanrossum, JelleZijlstra, sobolevn, kj, AlexWaygood
2022-01-29 16:53:37gvanrossumsetmessageid: <>
2022-01-29 16:53:37gvanrossumlinkissue46571 messages
2022-01-29 16:53:37gvanrossumcreate