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 GBeauregard
Recipients AlexWaygood, GBeauregard, JelleZijlstra, kj, serhiy.storchaka, sobolevn
Date 2022-02-06.17:25:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1644168328.23.0.889787539107.issue46642@roundup.psfhosted.org>
In-reply-to
Content
The issue in real code I had in mind was internal to cpython: if we remove the callable() check from _type_check naively, this test starts to fail. Both of our proposed changes happen to not fail this check. Given your second example, would you prefer if we remove this testcase if the issue comes up in the final proposed patches? On the other hand, there is precedent for giving this a nice error message other places in typing.py.
History
Date User Action Args
2022-02-06 17:25:28GBeauregardsetrecipients: + GBeauregard, serhiy.storchaka, JelleZijlstra, sobolevn, kj, AlexWaygood
2022-02-06 17:25:28GBeauregardsetmessageid: <1644168328.23.0.889787539107.issue46642@roundup.psfhosted.org>
2022-02-06 17:25:28GBeauregardlinkissue46642 messages
2022-02-06 17:25:28GBeauregardcreate