chore(deps): update dependency mock to v5 #875
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==4.0.3
->==5.0.0
Release Notes
testing-cabal/mock
v5.0.0
Compare Source
gh-98624: Add a mutex to unittest.mock.NonCallableMock to protect
concurrent access to mock attributes.
bpo-43478: Mocks can no longer be used as the specs for other Mocks. As a
result, an already-mocked object cannot have an attribute mocked using
autospec=True
or be the subject of acreate_autospec(...)
call. Thiscan uncover bugs in tests since these Mock-derived Mocks will always pass
certain tests (e.g. isinstance) and builtin assert functions (e.g.
assert_called_once_with) will unconditionally pass.
bpo-45156: Fixes infinite loop on :func:
unittest.mock.seal
of mockscreated by :func:
~unittest.create_autospec
.bpo-41403: Make :meth:
mock.patch
raise a :exc:TypeError
with arelevant error message on invalid arg. Previously it allowed a cryptic
:exc:
AttributeError
to escape.gh-91803: Fix an error when using a method of objects mocked with
:func:
unittest.mock.create_autospec
after it was sealed with:func:
unittest.mock.seal
function.bpo-41877: AttributeError for suspected misspellings of assertions on
mocks are now pointing out that the cause are misspelled assertions and
also what to do if the misspelling is actually an intended attribute name.
The unittest.mock document is also updated to reflect the current set of
recognised misspellings.
bpo-43478: Mocks can no longer be provided as the specs for other Mocks.
As a result, an already-mocked object cannot be passed to
mock.Mock()
.This can uncover bugs in tests since these Mock-derived Mocks will always
pass certain tests (e.g. isinstance) and builtin assert functions (e.g.
assert_called_once_with) will unconditionally pass.
bpo-45010: Remove support of special method
__div__
in:mod:
unittest.mock
. It is not used in Python 3.gh-84753: :func:
inspect.iscoroutinefunction
now properly returnsTrue
when an instance of :class:unittest.mock.AsyncMock
is passed toit. This makes it consistent with behavior of
:func:
asyncio.iscoroutinefunction
. Patch by Mehdi ABAAKOUK.bpo-46852: Remove the undocumented private
float.__set_format__()
method, previously known as
float.__setformat__()
in Python 3.7. Itsdocstring said: "You probably don't want to use this function. It exists
mainly to be used in Python's test suite." Patch by Victor Stinner.
gh-98086: Make sure
patch.dict()
can be applied on async functions.gh-100287: Fix the interaction of :func:
unittest.mock.seal
with:class:
unittest.mock.AsyncMock
.gh-83076: Instantiation of
Mock()
andAsyncMock()
is now 3.8xfaster.
bpo-41877: A check is added against misspellings of autospect, auto_spec
and set_spec being passed as arguments to patch, patch.object and
create_autospec.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.