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 JelleZijlstra, barry, eric.smith, gvanrossum, kj, larry, lukasz.langa, methane, xtreak
Date 2021-04-26.16:01:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'm not a big user of the inspect module, but I always thought that its use was so that you could look at a function (or other object) *produced by a 3rd party* and learn something about it.

Asking for the signature is one such operation, and I'd be rather upset if I couldn't inspect the annotation if that 3rd party happened to have added a bad string annotation. especially if I wasn't interested in the annotation part of the signature in the first place. (There's a lot of other useful info to be gleaned from it.)

OTOH I think it's fine for get_annotations() to raise by default if there's a bad annotation.
Date User Action Args
2021-04-26 16:01:30gvanrossumsetrecipients: + gvanrossum, barry, larry, eric.smith, methane, lukasz.langa, JelleZijlstra, xtreak, kj
2021-04-26 16:01:30gvanrossumsetmessageid: <>
2021-04-26 16:01:30gvanrossumlinkissue43817 messages
2021-04-26 16:01:30gvanrossumcreate