mock in kaste/mockito-python

What the code was meant to do, written into the code itself as a docstring

Create 'empty' objects ('Mocks'). Will create an empty unconfigured object, that you can pass around. All interactions (method calls) will be recorded and can be verified using :func:`verify` et.al. A plain `mock()` will be not `strict`, and thus all methods regardless of the arguments will return `None`. .. note:: Technically all attributes will return an internal interface. Because of that a simple `if mock().foo:` will surprisingly pass. If you set strict to `True`: `mock(strict=True)` all unexpected interactions will raise an error instead. You configure a mock using :func:`when`, :func:`when2` or :func:`expect`. You can also very conveniently just pass in a dict here:: response = mock({'text': 'ok', 'raise_for_status': lambda: None}) You can also create an empty Mock which is specced against a given `spec`: `mock(requests.Response)`. These mock are by default strict, thus they raise if you want to stub a method, the spec does not implement. Mockito will also match the function signature. You can pre-configure a specced mock as well:: response = mock({'json': lambda: {'status': 'Ok'}}, spec=requests.Response) Mocks are by default callable. Configure the callable behavior using `when`:: dummy = mock() when(dummy).__call__(1).thenReturn(2) All other magic methods must be configured this way or they will raise an AttributeError. See :func:`verify` to verify your interactions after usage.

The change

The check that tells the two apart

Check file tests/speccing_test.py, taken without changes from the fix and copied onto the older code, so the exact same check runs against both versions.