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 ramalho
Recipients docs@python, gvanrossum, levkivskyi, ramalho
Date 2020-07-14.01:43:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
After experimenting with theses protocols, I believe the user community is better served by leaving undocumented the fact that they are runtime checkable, because their runtime results are inconsistent with how Mypy handles them, producing both false positives and false negatives.

I've documented the problems ( and started two threads about them in the typing-sig mailing list:


Thread [1] got a useful partial response from Guido. Open questions remain. Thread [2] got no response at all.

I will gladly reengage in those threads or in this issue if there is interest. As it stands, I believe the use of the @runtime_checkable feature on several of these protocols is unreliable and should not be promoted.
Date User Action Args
2020-07-14 01:43:36ramalhosetrecipients: + ramalho, gvanrossum, docs@python, levkivskyi
2020-07-14 01:43:36ramalhosetmessageid: <>
2020-07-14 01:43:36ramalholinkissue40978 messages
2020-07-14 01:43:35ramalhocreate