Update mock requirement from ~=3.0.5 to ~=4.0.3

[dependabot[bot]]

Updates the requirements on mock to permit the latest version.

Changelog

Sourced from mock's changelog.

4.0.3

• Issue #42532: Remove unexpected call of __bool__ when passing a spec_arg argument to a Mock.

• Issue #39966: Revert bpo-25597. :class: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.

4.0.2

• Issue #39915: Ensure :attr:unittest.mock.AsyncMock.await_args_list has call objects in the order of awaited arguments instead of using :attr:unittest.mock.Mock.call_args which has the last value of the call. Patch by Karthikeyan Singaravelan.

4.0.1

• Remove the universal marker from the wheel.

4.0.0

• No Changes from 4.0.0b1.

4.0.0b1

• The release is a fresh cut of cpython's 4a686504__. All changes to :mod:mock from that commit and before are included in this release along with the subsequent changes listed below.

  __ https://github.com/python/cpython/commit/4a686504eb2bbf69adf78077458508a7ba131667

• 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')

... (truncated)

Commits

• 93cf533 Preparing for 4.0.3 release.
• 841c331 latest sync point
• f7e3ea8 bpo-42532: Check if NonCallableMock's spec_arg is not None instead of call it...
• e5d7551 bpo-41877 Check for asert, aseert, assrt in mocks (GH-23165)
• c627515 bpo-39966: Revert "bpo-25597: Ensure wraps' return value is used for magic me...
• 902eea1 bpo-40126: Fix reverting multiple patches in unittest.mock. (GH-19351)
• a7002f3 Update issue templates
• 27d6349 pytest-dev/pytest#6924
• b5ce0a5 Add intersphinx.
• 87546bf Preparing for 4.0.2 release.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.