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 2010-03-02.13:57:43
SpamBayes Score 0.00156828
Marked as misclassified No
Message-id <>
Originally reported as a bug against unittest2:

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...
Date User Action Args
2010-03-02 13:57:46michael.foordsetrecipients: + michael.foord
2010-03-02 13:57:46michael.foordsetmessageid: <>
2010-03-02 13:57:44michael.foordlinkissue8038 messages
2010-03-02 13:57:43michael.foordcreate