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 simon.percivall
Recipients levkivskyi, simon.percivall
Date 2017-04-11.21:23:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
It think it's important to document this caveat in `get_type_hints`, that there is virtually _no_ way to use it safely with a class, and that there will always be a high risk of getting an exception unless using this function in a highly controlled setting.

This also, as a consequence, means that there is no "best-effort" support for collecting type hints from a class hierarchy, and every instance of trying to use this function with classes, or traversing __annotations__ "manually", will need to be solved ad-hoc and from scratch by the user (until someone publishes a "typing-utils" package on PyPI).
Date User Action Args
2017-04-11 21:23:34simon.percivallsetrecipients: + simon.percivall, levkivskyi
2017-04-11 21:23:34simon.percivallsetmessageid: <>
2017-04-11 21:23:34simon.percivalllinkissue29966 messages
2017-04-11 21:23:33simon.percivallcreate