[issue35077] Make TypeError message less ambiguous

[coyot linden]

coyot linden <coyot at lindenlab.com> added the comment:

The problem I have with "So only the 'index of string' interpretation makes sense." is that by the time a developer has that understanding, they won't get this error. So it's fine and logical to say from the behind-the-scenes view that only sequences talk about indices, but that's not helpful to the confused developer who gets this message. The point of error messages should be to clearly indicate the problem and solution, not rely on the developer having a global understanding of error messages.

So, rather than defend the current practice, I ask if there are arguments against "X of Y". Is there some context in which that is confusing?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35077>
_______________________________________