Noted, yes this was more just a QOL improvement suggestion by me as it strikes me as a useful breadcrumb that could be left to help to the developer get to the bottom of where it's come from especially when debugging bad code like this.
The faster they can find where the bad code is and refactor it as you suggested above, the better. And if it's a trivial change, all the better. Obviously coding around the Exception's error message would be madness but making it a bit more explicit about the specific error is always useful especially as not all tools such as Sentry will support that new REPL underlining indicator out of the box. --- [Visit Topic](https://discuss.python.org/t/small-suggestion-regarding-type-errors-and-subscription/67898/14) or reply to this email to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.python.org/email/unsubscribe/3ecf8c023d73ce46d492f84d3a16f32739ae3fee8beefb9e183511524ad095b0).
