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
Date 2009-04-02.01:58:33
SpamBayes Score 5.8461302e-09
Marked as misclassified No
Message-id <1238637520.24.0.827171540397.issue5663@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2009-04-02 01:58:41michael.foordsetrecipients: + michael.foord
2009-04-02 01:58:40michael.foordsetmessageid: <1238637520.24.0.827171540397.issue5663@psf.upfronthosting.co.za>
2009-04-02 01:58:39michael.foordlinkissue5663 messages
2009-04-02 01:58:37michael.foordcreate