Message291517
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:34 | simon.percivall | set | recipients:
+ simon.percivall, levkivskyi |
2017-04-11 21:23:34 | simon.percivall | set | messageid: <1491945814.03.0.202540956309.issue29966@psf.upfronthosting.co.za> |
2017-04-11 21:23:34 | simon.percivall | link | issue29966 messages |
2017-04-11 21:23:33 | simon.percivall | create | |
|