This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author bignose
Recipients Julian.Gindi, Tim.Graham, berker.peksag, bignose, brett.cannon, davidszotten@gmail.com, eric.snow, ezio.melotti, ncoghlan, rhettinger, serhiy.storchaka
Date 2016-10-12.19:37:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20161012193108.eunreofyblrb2nys@benfinney.id.au>
In-reply-to <1476283782.88.0.232291094622.issue21720@psf.upfronthosting.co.za>
Content
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
expected.

That is, the error message should say exactly what type is expected
*and* exactly what type failed that check.
History
Date User Action Args
2016-10-12 19:37:11bignosesetrecipients: + bignose, brett.cannon, rhettinger, ncoghlan, ezio.melotti, eric.snow, berker.peksag, serhiy.storchaka, Julian.Gindi, davidszotten@gmail.com, Tim.Graham
2016-10-12 19:37:11bignoselinkissue21720 messages
2016-10-12 19:37:11bignosecreate