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 akaptur
Recipients Wilfred.Hughes, akaptur, michael.foord, r.david.murray
Date 2015-09-04.04:24:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441340649.55.0.567028046391.issue24857@psf.upfronthosting.co.za>
In-reply-to
Content
It looks like there's a related bug in call_args around __ne__:

>>> m = Mock()
>>> m(1,2)
<Mock name='mock()' id='4483976016'>
>>> m.call_args
call(1, 2)
>>> m.call_args == call(1,2)
True
>>> m.call_args != call(1,2)
True

Any reason not to define __ne__ as not __eq__? Otherwise it looks like you fall back to tuple.__ne__, which does the wrong thing here.
History
Date User Action Args
2015-09-04 04:24:09akaptursetrecipients: + akaptur, r.david.murray, michael.foord, Wilfred.Hughes
2015-09-04 04:24:09akaptursetmessageid: <1441340649.55.0.567028046391.issue24857@psf.upfronthosting.co.za>
2015-09-04 04:24:09akapturlinkissue24857 messages
2015-09-04 04:24:09akapturcreate