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 michael.foord
Recipients michael.foord, michael.foord
Date 2009-04-02.02:02:23
SpamBayes Score 8.27392e-08
Marked as misclassified No
Message-id <>
Reviewers: ,

Patch for unittest on trunk.

It provides better default failure messages for assertTrue and
assertFalse (current is "AssertionError: None").

It also provides a new class attribute for TestCase: longMessage

This defaults to False. If set to True, passing in an explicit custom
message does *not* override the helpful default failure message in
asserts which tell you which objects were involved in the failure.

Even if set to True or False in a TestCase then longMessage can still be
overridden in individual tests by setting an instance attribute.

Needs docs.

Could longMessage default to True in 3.1?

Please review this at

Affected files:
Date User Action Args
2009-04-02 02:02:24fuzzymansetrecipients: + michael.foord
2009-04-02 02:02:23fuzzymanlinkissue5663 messages
2009-04-02 02:02:23fuzzymancreate