On Sun, Feb 16, 2014 at 12:22 AM, Nick Coghlan <[email protected]> wrote:
> The practical benefits of this kind of change in the test suite are > also highly dubious, because they *only help if the test fails at some > point in the future*. At that point, whoever caused the test to fail > will switch into debugging mode, and a couple of relevant points > apply: > One place where those points don't apply so cleanly is when the test failure is coming from continuous integration and can't easily be reproduced locally (e.g., because there's a problem on a platform you don't have access to, or because it's some kind of threading-related intermittent failure that's exacerbated by the timing conditions on a particular machine). In those situations, an informative error message can easily save significant debugging time. Count me as +1 on the test updates, provided they're done carefully. (And all those I've looked at from Serhiy do indeed look careful.) -- Mark
_______________________________________________ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com