<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">>. There's nothing mysterious about e.g. `TypeError: unsupported operand type(s) for +: 'int' and 'str'`, unlike the case of the two concatenated tuples. (Surely people get errors about int+str all the time, and they've never complained -- unlike the tuple tuple case.)<div><br></div><div>Well, yes, that particular example is pretty clear. But as a rule, there are a LOT of errors that can be pretty mysterious to newbies.</div><div><br></div><div>I would love to see Python become generally more informative with errors. </div><div><br></div><div>In this case, you’d probably get a similar error, but it’s still nice to get it sooner, and if the hooks are in place, We could have others that are really helpful.</div><div><br></div><div>-CHB</div><div><br></div><div><br><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Is there value in distinguishing<br>
"InevitableTypeError" from "InevitableAttributeError"?<br></blockquote></div></div></div></div></blockquote><div><br></div><div>I don’t think so — what we need are helpful error messages. If it will be raised at compile time, then it won’t generally be catchable in s try-except— so the actual exception type isn’t very important.</div><div><br></div><div>-CHB</div><div><br></div></div></body></html>