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 aplummer
Recipients aplummer, felixonmars, michael.foord
Date 2016-02-08.00:02:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I've had a look and I think this could be because the class _Call (also in unittest.mock) has lost its __ne__ method between 3.4 and 3.5.


This leads me to this changeset:

My failing test:

from unittest import mock

call1 =
call2 =

assert call1 == call2
assert not (call1 != call2)

This passes in 3.4 but fails in 3.5, but fails on the second assert, not the first. So they are equal, but they're not not-equal. I've added this as a test and reinstated __ne__ in my patch.
Date User Action Args
2016-02-08 00:02:58aplummersetrecipients: + aplummer, michael.foord, felixonmars
2016-02-08 00:02:58aplummersetmessageid: <>
2016-02-08 00:02:58aplummerlinkissue25195 messages
2016-02-08 00:02:57aplummercreate