From 283f1aa881af1c887fa90af914b51577c1b34461 Mon Sep 17 00:00:00 2001 From: Berker Peksag Date: Wed, 7 Jan 2015 21:15:02 +0200 Subject: Issue #20487: Clarify meaning of "side effect" in the magic mock documentation. Patch by A.M. Kuchling. --- Doc/library/unittest.mock.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Doc/library/unittest.mock.rst b/Doc/library/unittest.mock.rst index f92353c..b242438 100644 --- a/Doc/library/unittest.mock.rst +++ b/Doc/library/unittest.mock.rst @@ -1678,9 +1678,10 @@ For example: >>> object() in mock False -The two equality method, :meth:`__eq__` and :meth:`__ne__`, are special. -They do the default equality comparison on identity, using a side -effect, unless you change their return value to return something else: +The two equality methods, :meth:`__eq__` and :meth:`__ne__`, are special. +They do the default equality comparison on identity, using the +:attr:`~Mock.side_effect` attribute, unless you change their return value to +return something else:: >>> MagicMock() == 3 False -- cgit v0.12