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.

Title: equality surprisingly broken
Type: behavior Stage: resolved
Components: Tests Versions: Python 3.8, Python 3.7, Python 2.7
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: michael.foord Nosy List: cjw296, dfortunov, eric.araujo, mariocj89, michael.foord, xtreak
Priority: normal Keywords: patch

Created on 2018-11-13 08:05 by cjw296, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 10555 merged python-dev, 2018-11-15 06:57
PR 10878 merged miss-islington, 2018-12-03 21:32
PR 10879 merged miss-islington, 2018-12-03 21:32
Messages (13)
msg329813 - (view) Author: Chris Withers (cjw296) * (Python committer) Date: 2018-11-13 08:05
$ python3
Python 3.7.0 (v3.7.0:1bf9cc5093, Jun 26 2018, 23:26:24) 
[Clang 6.0 (clang-600.0.57)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from unittest.mock import call
>>> call(x=1) == call(x=2)

Good so far?

>>> call(x=1).foo == call(x=2).foo

Eep, I think a lot of people might find that quite surprising!
msg329820 - (view) Author: Karthikeyan Singaravelan (xtreak) * (Python committer) Date: 2018-11-13 09:53
I think this is due to the fact that when an attribute of a call object is accessed a new call object is returned with the parent as self.parent [0] but the original information regarding the parent is lost during representation and no check for self.parent equality while the call objects are compared [1]

Python 3.8.0a0 (heads/master:0dc1e45dfd, Nov 13 2018, 11:19:49)
[Clang 7.0.2 (clang-700.1.81)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from unittest.mock import call
>>> call(x=2).foo
>>> call(x=1).foo
>>> # Comparison returns true since it's similar to call().foo == call().foo though parents are set
>>> call(x=1).foo == call(x=2).foo
>>> call(x=1).foo.parent
>>> call(x=2).foo.parent
>>> call(x=2).foo(x=2).bar
>>> call(x=4).foo(x=3).bar
>>> # Comparison returns true since it's similar to call().foo().bar == call().foo().bar
>>> call(x=2).foo(x=2).bar == call(x=4).foo(x=3).bar 
>>> call(x=4).foo(x=3).bar.parent

Maybe we can add a check for parent to be equal if present? 

diff --git a/Lib/unittest/ b/Lib/unittest/
index a9c82dcb5d..a7565d5f60 100644
--- a/Lib/unittest/
+++ b/Lib/unittest/
@@ -2054,6 +2054,10 @@ class _Call(tuple):
             self_name, self_args, self_kwargs = self

+        if (getattr(self, 'parent', None) and getattr(other, 'parent', None)
+            and self.parent != other.parent):
+            return False
         other_name = ''
         if len_other == 0:
             other_args, other_kwargs = (), {}

With patch the checks return False and there is no test suite failure but I am not sure if I need to put this inside a while loop to check for nested parents and there maybe other cases that my code doesn't handle.

➜  cpython git:(master) ✗ ./python.exe -c 'from unittest.mock import call; print(call(x=2) == call(x=1)'
➜  cpython git:(master) ✗ ./python.exe -c 'from unittest.mock import call; print(call(x=2).foo == call(x=1).foo)'

msg329821 - (view) Author: Chris Withers (cjw296) * (Python committer) Date: 2018-11-13 10:01
I don't think the getattr(self, 'parent', None) is necessary, the attribute is always there and None == None ;-)

I reckon this will work:

if self.parent != other.parent):
    return True

...but obviously, we'd add some more tests to the suite to make sure this keeps working.

If this is the way to go, lemme know and I'll work up a PR.
msg329823 - (view) Author: Karthikeyan Singaravelan (xtreak) * (Python committer) Date: 2018-11-13 10:26
Yes, for call objects it's always there but some of the tests use a tuple during self.assertEquals and hence during equality check other fails with the attribute error for parent like below. Also getattr(self, 'parent', None) != getattr(other, 'parent', None) will skip the attribute error but still fail for tuples in tests I guess with tuple.parent returned as None and checked against a valid parent. Hence the patch with both the checks of getattr and self.parent that passes the test suite. I will wait for input from maintainers if my approach is correct since I am little new to mock :)

ERROR: test_explicit_mock (unittest.test.testmock.testwith.TestMockOpen)
Traceback (most recent call last):
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Lib/unittest/test/testmock/", line 177, in test_explicit_mock
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Lib/unittest/", line 838, in assert_called_once_with
    return self.assert_called_with(*args, **kwargs)
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Lib/unittest/", line 823, in assert_called_with
    if expected != actual:
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Lib/unittest/", line 2057, in __eq__
    if self.parent != other.parent:
AttributeError: 'tuple' object has no attribute 'parent'
msg329825 - (view) Author: Mario Corchero (mariocj89) * (Python triager) Date: 2018-11-13 11:27
If this is to be done we should not change those tests, I am sure there is code validating calls relying on its "tupleness". Example:


>>> import unittest.mock
>>> m = unittest.mock.Mock()
>>> m(1)
>>> m(2, a=1) 
>>> m.assert_has_calls([
...   ((1,), {}),
...   ((2,), {'a':1}),
... ])


This is documented here:

On the addition in general,
I cannot really comment on the "call(x=1).foo == call(x=2).foo" or how that is supposed to work, I've used those "nesting calls" minimally. I would try to get a hold of Michael Ford.

As a note, I think nesting calls in is supposed to be used only via the method and for calls only.


>>> call(x=1).foo(z=1).call_list() == call(x=1).foo(z=1).call_list()
>>> call(x=2).foo(z=1).call_list() == call(x=1).foo(z=1).call_list()

which "works as expected".

Having support for:

```call(x=1).foo == call(x=2).foo``` is kind of trying to validate an attribute has been accessed, which is a different thing from what mock.calls seems to be doing at the moment. It could be added I guess, but I don't see how do can you use that in `mock.assert_has_calls` for example. What is the "real life" issue that you faced with this issue? Because creating and comparing calls yourself is not something that is usually done, I guess you compared it to a mock call.
msg329826 - (view) Author: Chris Withers (cjw296) * (Python committer) Date: 2018-11-13 11:31
I'm chatting with Michael already (on Facebook of all places), and I use this feature heavily and deeply, being one of the people who originally requested it.

I'm both happy and capable of seeing this through, so no need for anyone else to dive in :-)

Hopefully Michael will follow up when he gets a chance...
msg329827 - (view) Author: Michael Foord (michael.foord) * (Python committer) Date: 2018-11-13 11:39
Parents comparing upwards sounds like the right (and simple) fix. Not breaking the tuple tests would be good. I'm happy for Chris to produce the patch.
msg329945 - (view) Author: Chris Withers (cjw296) * (Python committer) Date: 2018-11-15 07:50
Assuming the PR is merged, what do I need to do for 3.7 and 3.6 backports?
There's no doubt a doc for this somewhere, so please just point me at it :-)
msg330008 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2018-11-16 18:27
Add the right «needs backport to X.Y» labels to the PR and a bot will take care of it.

(This info does not seem to be in the devguide!)
msg330577 - (view) Author: Chris Withers (cjw296) * (Python committer) Date: 2018-11-28 07:42
Éric, doesn't look like I can add labels, what needs to happen for me to do so? (I was/am a core developer, just an extremely inactive one ;-), but happy to jump through whatever hoops necessary... )
msg330983 - (view) Author: Chris Withers (cjw296) * (Python committer) Date: 2018-12-03 21:31
New changeset 8ca0fa9d2f4de6e69f0902790432e0ab2f37ba68 by Chris Withers in branch 'master':
bpo-35226: Fix equality for nested objects. (#10555)
msg330984 - (view) Author: Chris Withers (cjw296) * (Python committer) Date: 2018-12-03 21:54
New changeset 67e6136a6d5c07141d4dba820c450a70db7aedd5 by Chris Withers (Miss Islington (bot)) in branch '3.6':
bpo-35226: Fix equality for nested objects. (GH-10555)
msg330985 - (view) Author: Chris Withers (cjw296) * (Python committer) Date: 2018-12-03 21:54
New changeset e8f9e4785caeef8a68bb7859280e91a4cb424b79 by Chris Withers (Miss Islington (bot)) in branch '3.7':
bpo-35226: Fix equality for nested objects. (GH-10555)
Date User Action Args
2022-04-11 14:59:08adminsetgithub: 79407
2018-12-03 22:01:20cjw296setstatus: open -> closed
stage: patch review -> resolved
2018-12-03 21:54:47cjw296setmessages: + msg330985
2018-12-03 21:54:24cjw296setmessages: + msg330984
2018-12-03 21:32:32miss-islingtonsetpull_requests: + pull_request10118
2018-12-03 21:32:23miss-islingtonsetpull_requests: + pull_request10117
2018-12-03 21:31:40cjw296setmessages: + msg330983
2018-12-02 14:21:17dfortunovsetnosy: + dfortunov
2018-11-28 07:42:41cjw296setmessages: + msg330577
2018-11-16 18:27:48eric.araujosetnosy: + eric.araujo
messages: + msg330008
2018-11-15 07:50:24cjw296setmessages: + msg329945
2018-11-15 06:57:19python-devsetkeywords: + patch
stage: patch review
pull_requests: + pull_request9798
2018-11-13 11:39:44michael.foordsetmessages: + msg329827
2018-11-13 11:31:40cjw296setmessages: + msg329826
2018-11-13 11:27:55mariocj89setmessages: + msg329825
2018-11-13 10:26:26xtreaksetmessages: + msg329823
2018-11-13 10:01:48cjw296setmessages: + msg329821
2018-11-13 09:59:01vstinnersetnosy: + mariocj89
2018-11-13 09:53:22xtreaksetnosy: + xtreak
messages: + msg329820
2018-11-13 08:05:32cjw296create