--- /tmp/python-mock-4.0.3-1ux7drmce/debian/python-mock-doc_4.0.3-1_all.deb +++ python-mock-doc_4.0.3-1_all.deb ├── control.tar.xz │ ├── control.tar │ │ ├── ./md5sums │ │ │ ├── ./md5sums │ │ │ │┄ Files differ ├── data.tar.xz │ ├── data.tar │ │ ├── ./usr/share/doc/python-mock-doc/html/changelog.html │ │ │ @@ -41,31 +41,31 @@ │ │ │
Issue #42532: Remove unexpected call of __bool__
when passing a
│ │ │ spec_arg
argument to a Mock.
Issue #39966: Revert bpo-25597. unittest.mock.MagicMock
with
│ │ │ +
Issue #39966: Revert bpo-25597. unittest.mock.MagicMock
with
│ │ │ wraps’ set uses default return values for magic methods.
Issue #41877: Mock objects which are not unsafe will now raise an │ │ │ AttributeError if an attribute with the prefix asert, aseert, or assrt is │ │ │ accessed, in addition to this already happening for the prefixes assert or │ │ │ assret.
Issue #40126: Fixed reverting multiple patches in unittest.mock. Patcher’s
│ │ │ __exit__()
is now never called if its __enter__()
is failed.
│ │ │ Returning true from __exit__()
silences now the exception.
Issue #39915: Ensure unittest.mock.AsyncMock.await_args_list
has
│ │ │ +
Issue #39915: Ensure unittest.mock.AsyncMock.await_args_list
has
│ │ │ call objects in the order of awaited arguments instead of using
│ │ │ -unittest.mock.Mock.call_args
which has the last value of the call.
│ │ │ +unittest.mock.Mock.call_args
which has the last value of the call.
│ │ │ Patch by Karthikeyan Singaravelan.
Remove the universal marker from the wheel.
Issue #37972: Subscripts to the unittest.mock.call objects now receive │ │ │ the same chaining mechanism as any other custom attributes, so that the │ │ │ following usage no longer raises a TypeError:
│ │ │call().foo().__getitem__(‘bar’)
│ │ │Patch by blhsing
│ │ │Issue #38839: Fix some unused functions in tests. Patch by Adam Johnson.
Issue #39485: Fix a bug in unittest.mock.create_autospec()
that
│ │ │ +
Issue #39485: Fix a bug in unittest.mock.create_autospec()
that
│ │ │ would complain about the wrong number of arguments for custom descriptors
│ │ │ defined in an extension module returning functions.
Issue #39082: Allow AsyncMock to correctly patch static/class methods
Issue #38093: Fixes AsyncMock so it doesn’t crash when used with │ │ │ AsyncContextManagers or AsyncIterators.
Issue #38859: AsyncMock now returns StopAsyncIteration on the exaustion of │ │ │ a side_effects iterable. Since PEP-479 its Impossible to raise a │ │ │ @@ -113,18 +113,18 @@ │ │ │ documentation around this.
Issue #37555: Fix NonCallableMock._call_matcher returning tuple instead │ │ │ of _Call object when self._spec_signature exists. Patch by Elizabeth │ │ │ Uselton
Issue #37251: Remove __code__ check in AsyncMock that incorrectly │ │ │ evaluated function specs as async objects but failed to evaluate classes │ │ │ with __await__ but no __code__ attribute defined as async objects.
Issue #38669: Raise TypeError
when passing target as a string with
│ │ │ +
Issue #38669: Raise TypeError
when passing target as a string with
│ │ │ unittest.mock.patch.object()
.
Issue #25597: Ensure, if wraps
is supplied to
│ │ │ -unittest.mock.MagicMock
, it is used to calculate return values
│ │ │ +unittest.mock.MagicMock
, it is used to calculate return values
│ │ │ for the magic methods instead of using the default return values. Patch by
│ │ │ Karthikeyan Singaravelan.
Issue #38108: Any synchronous magic methods on an AsyncMock now return a │ │ │ MagicMock. Any asynchronous magic methods on a MagicMock now return an │ │ │ AsyncMock.
Issue #21478: Record calls to parent when autospecced object is attached
│ │ │ to a mock using unittest.mock.attach_mock()
. Patch by Karthikeyan
│ │ │ @@ -132,22 +132,22 @@
│ │ │
Issue #38857: AsyncMock fix for return values that are awaitable types. │ │ │ This also covers side_effect iterable values that happend to be awaitable, │ │ │ and wraps callables that return an awaitable type. Before these awaitables │ │ │ were being awaited instead of being returned as is.
Issue #38932: Mock fully resets child objects on reset_mock(). Patch by │ │ │ Vegard Stikbakke
Issue #37685: Fixed __eq__
, __lt__
etc implementations in some
│ │ │ -classes. They now return NotImplemented
for unsupported type of
│ │ │ +classes. They now return NotImplemented
for unsupported type of
│ │ │ the other operand. This allows the other operand to play role (for example
│ │ │ -the equality comparison with ANY
will return
│ │ │ +the equality comparison with ANY
will return
│ │ │ True
).
Issue #37212: unittest.mock.call()
now preserves the order of
│ │ │ +
Issue #37212: unittest.mock.call()
now preserves the order of
│ │ │ keyword arguments in repr output. Patch by Karthikeyan Singaravelan.
Issue #37828: Fix default mock name in
│ │ │ -unittest.mock.Mock.assert_called()
exceptions. Patch by Abraham
│ │ │ +unittest.mock.Mock.assert_called()
exceptions. Patch by Abraham
│ │ │ Toriz Cruz.
Issue #36871: Improve error handling for the assert_has_calls and │ │ │ assert_has_awaits methods of mocks. Fixed a bug where any errors │ │ │ encountered while binding the expected calls to the mock’s spec were │ │ │ silently swallowed, leading to misleading error output.
Issue #21600: Fix mock.patch.stopall()
to stop active patches that
│ │ │ were created with mock.patch.dict()
.
Issue #31855: unittest.mock.mock_open()
results now respects the
│ │ │ +
Issue #31855: unittest.mock.mock_open()
results now respects the
│ │ │ argument of read([size]). Patch contributed by Rémi Lapeyre.
Include the license, readme and changelog in the source distribution.
Issue #35226: Recursively check arguments when testing for equality of
│ │ │ unittest.mock.call
objects and add note that tracking of
│ │ │ parameters used to create ancestors of mocks in mock_calls
is not
│ │ │ possible.
Issue #31177: Fix bug that prevented using reset_mock
on mock instances with deleted attributes
Issue #31177: Fix bug that prevented using reset_mock
on mock instances with deleted attributes
Issue #26704: Added test demonstrating double-patching of an instance │ │ │ method. Patch by Anthony Sottile.
Issue #35500: Write expected and actual call parameters on separate lines
│ │ │ -in unittest.mock.Mock.assert_called_with()
assertion errors.
│ │ │ +in unittest.mock.Mock.assert_called_with()
assertion errors.
│ │ │ Contributed by Susan Su.
Issue #35330: When a Mock
instance was used to wrap an object, if
│ │ │ side_effect is used in one of the mocks of it methods, don’t call the
│ │ │ original implementation and return the result of using the side effect the
│ │ │ same way that it is done with return_value.
Issue #30541: Add new function to seal a mock and prevent the │ │ │ automatically creation of child mocks. Patch by Mario Corchero.
Issue #35022: unittest.mock.MagicMock
now supports the
│ │ │ -__fspath__
method (from os.PathLike
).
Issue #33516: unittest.mock.MagicMock
now supports the
│ │ │ +
Issue #35022: unittest.mock.MagicMock
now supports the
│ │ │ +__fspath__
method (from os.PathLike
).
Issue #33516: unittest.mock.MagicMock
now supports the
│ │ │ __round__
magic method.
Issue #35512: unittest.mock.patch.dict()
used as a decorator with
│ │ │ +
Issue #35512: unittest.mock.patch.dict()
used as a decorator with
│ │ │ string target resolves the target during function call instead of during
│ │ │ decorator construction. Patch by Karthikeyan Singaravelan.
Issue #36366: Calling stop()
on an unstarted or stopped
│ │ │ -unittest.mock.patch()
object will now return None instead of
│ │ │ -raising RuntimeError
, making the method idempotent. Patch
│ │ │ +unittest.mock.patch()
object will now return None instead of
│ │ │ +raising RuntimeError
, making the method idempotent. Patch
│ │ │ byKarthikeyan Singaravelan.
Issue #35357: Internal attributes’ names of unittest.mock._Call and │ │ │ unittest.mock.MagicProxy (name, parent & from_kall) are now prefixed with │ │ │ _mock_ in order to prevent clashes with widely used object attributes. │ │ │ Fixed minor typo in test function name.
Issue #20239: Allow repeated assignment deletion of
│ │ │ -unittest.mock.Mock
attributes. Patch by Pablo Galindo.
unittest.mock.Mock
attributes. Patch by Pablo Galindo.
│ │ │ Issue #35082: Don’t return deleted attributes when calling dir on a
│ │ │ -unittest.mock.Mock
.
unittest.mock.Mock
.
│ │ │ Issue #0: Improved an error message when mock assert_has_calls fails.
Issue #23078: Add support for classmethod()
and staticmethod()
│ │ │ -to unittest.mock.create_autospec()
. Initial patch by Felipe Ochoa.
Issue #23078: Add support for classmethod()
and staticmethod()
│ │ │ +to unittest.mock.create_autospec()
. Initial patch by Felipe Ochoa.
Issue #21478: Calls to a child function created with
│ │ │ -unittest.mock.create_autospec()
should propagate to the parent.
│ │ │ +unittest.mock.create_autospec()
should propagate to the parent.
│ │ │ Patch by Karthikeyan Singaravelan.
Issue #36598: Fix isinstance
check for Mock objects with spec when the
│ │ │ code is executed under tracing. Patch by Karthikeyan Singaravelan.
Issue #32933: unittest.mock.mock_open()
now supports iteration over
│ │ │ +
Issue #32933: unittest.mock.mock_open()
now supports iteration over
│ │ │ the file contents. Patch by Tony Flury.
Issue #21269: Add args
and kwargs
properties to mock call objects.
│ │ │ Contributed by Kumar Akshay.
Issue #17185: Set __signature__
on mock for inspect
to get
│ │ │ +
Issue #17185: Set __signature__
on mock for inspect
to get
│ │ │ signature. Patch by Karthikeyan Singaravelan.
Issue #35047: unittest.mock
now includes mock calls in exception
│ │ │ messages if assert_not_called
, assert_called_once
, or
│ │ │ assert_called_once_with
fails. Patch by Petter Strandmark.
Issue #28380: unittest.mock Mock autospec functions now properly support │ │ │ assert_called, assert_not_called, and assert_called_once.
Issue #28735: Fixed the comparison of mock.MagickMock with mock.ANY.