Ben Finney added the comment:
On 12-Oct-2016, Nick Coghlan wrote:
> In this case, I think just reporting the first failing item is fine,
> and mentioning the type of that item in the error message is the
> most useful additional information we can provide to make things
> easier to debug.
Yes; also, the type expected, so the user knows what's different from
That is, the error message should say exactly what type is expected
*and* exactly what type failed that check.
Python tracker <rep...@bugs.python.org>
Python-bugs-list mailing list