[issue8038] Not all the new assert* unittest.TestCase methods have negative (not) equivalents

[Ryszard Szopa]

Ryszard Szopa <ryszard.szopa at gmail.com> added the comment:

Hi,

I am the original reporter of the bug. Please forgive me if this is not the place for discussing the issue. 

I've thought about it, and stuff like assertDictNotEqual or assertSequenceNotEqual aren't really necessary - it is much easier (and shorter) to use assertNotEqual, and there's no need for any special formatting needed to say that something is equal when it shouldn't.

This is not the case for assertNotRegexpMatches, though. assertNot(re.match(...)) tells me only that False is not True. I'd like it to say *how* the text matches the regex (the matching part that is). (Sorry for repeating myself, I try to be clearer this time.)

So, this issue could be renamed to "Implement assertNotRegexpMatches."

----------
nosy: +Ryszard.Szopa

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue8038>
_______________________________________