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, Gobot1234, JelleZijlstra, gvanrossum, kj, levkivskyi, serhiy.storchaka, sobolevn
Date 2022-02-06.20:28:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1644179335.08.0.163644871148.issue46644@roundup.psfhosted.org>
In-reply-to
Content
I compiled your PR to run it and was testing in 3.10 as well, but I was testing in a file with from __future__ import annotations unintentionally. I retract the comment. It turns out `list[42]` is okay though, which I suppose is more relevant going forward. My confusion here is sort of the crux of my problem with these runtime checks: they are inconsistently applied in different locations which is why callable() was causing a lot of bugs.
History
Date User Action Args
2022-02-06 20:28:55GBeauregardsetrecipients: + GBeauregard, gvanrossum, serhiy.storchaka, levkivskyi, JelleZijlstra, sobolevn, Gobot1234, kj, AlexWaygood
2022-02-06 20:28:55GBeauregardsetmessageid: <1644179335.08.0.163644871148.issue46644@roundup.psfhosted.org>
2022-02-06 20:28:55GBeauregardlinkissue46644 messages
2022-02-06 20:28:55GBeauregardcreate