Author michael.foord
Recipients michael.foord
Date 2010-03-02.13:57:43
SpamBayes Score 0.00156828
Marked as misclassified No
Message-id <1267538266.49.0.841042020206.issue8038@psf.upfronthosting.co.za>
In-reply-to
Content
Originally reported as a bug against unittest2: http://code.google.com/p/unittest-ext/issues/detail?id=3

There are some assert* methods that don't have their assertNot* 
counterparts. There's assertDictEqual, assertSequenceEqual, 
assertRegexpMatches, but no assertDictNotEqual, assertSequenceNotEqual, 
assertRegexpNotMatches, for example.

They should be present for the sake of completeness (I don't like to have to look into the docs to check if a method has a negative counterpart), but also because they ask for a custom output. For example, the error accompanying assertRegexpNotMatches could show the matching part of the text, which is the part that really interests me. assert_(re.match(...)) will only tell me that None is not true...
History
Date User Action Args
2010-03-02 13:57:46michael.foordsetrecipients: + michael.foord
2010-03-02 13:57:46michael.foordsetmessageid: <1267538266.49.0.841042020206.issue8038@psf.upfronthosting.co.za>
2010-03-02 13:57:44michael.foordlinkissue8038 messages
2010-03-02 13:57:43michael.foordcreate