[issue16433] unittest.TestCase.assertNotEqual has incorrect docstring.

Andrew Svetlov added the comment: Oops. Sorry, my fault. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue16433] unittest.TestCase.assertNotEqual has incorrect docstring.

Mark Dickinson added the comment: Andrew: if the objects are not equal, the test should pass, not fail. -- ___ Python tracker ___ ___

[issue16433] unittest.TestCase.assertNotEqual has incorrect docstring.

Andrew Svetlov added the comment: Maybe better to use: Fail if the two objects are *not* equal as determined by the '!=' operator. ??? -- nosy: +asvetlov ___ Python tracker ___

[issue16433] unittest.TestCase.assertNotEqual has incorrect docstring.

Mark Dickinson added the comment: Thanks, Ezio! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue16433] unittest.TestCase.assertNotEqual has incorrect docstring.

Ezio Melotti added the comment: Fixed, thanks for the report! -- assignee: -> ezio.melotti nosy: +ezio.melotti resolution: -> fixed stage: -> committed/rejected status: open -> closed type: -> enhancement ___ Python tracker

[issue16433] unittest.TestCase.assertNotEqual has incorrect docstring.

Roundup Robot added the comment: New changeset d32d04edd371 by Ezio Melotti in branch '2.7': #16433: fix docstring of assertNotEqual. http://hg.python.org/cpython/rev/d32d04edd371 New changeset 9d5cc978cfe5 by Ezio Melotti in branch '3.2': #16433: fix docstring of assertNotEqual. http://hg.pytho

[issue16433] unittest.TestCase.assertNotEqual has incorrect docstring.

New submission from Mark Dickinson: The TestCase.assertNotEqual docstring currently says: Fail if the two objects are equal as determined by the '==' operator. This doesn't match the implementation, which checks that '!=' gives True (rather than checking that '==' gives False). The online d