Tuesday, August 04, 2020

Identifying misleading type hints

Yesterday on Twitter:


For beginners, unintentional type hints can be really confusing.  No SyntaxError, no traceback to guide the beginners ... Still, could Friendly-traceback help?



I've already mentioned how Friendly-traceback could be used by Thonny, and how it could also be used with Mu.  What about IDLE?



Yes, it can.  And what if it is typos and not type hints that are causing problems?




Note: This is freshly written code. The documentation really needs to be updated to reflect the most recent changes.

No comments: