Bump mock from 2.0.0 to 5.0.2

[dependabot[bot]]

Bumps mock from 2.0.0 to 5.0.2.

Changelog

Sourced from mock's changelog.

5.0.2

• gh-102978: Fixes :func:unittest.mock.patch not enforcing function signatures for methods decorated with @classmethod or @staticmethod when patch is called with autospec=True.

• gh-103329: Regression tests for the behaviour of unittest.mock.PropertyMock were added.

5.0.1

• gh-100740: Fix unittest.mock.Mock not respecting the spec for attribute names prefixed with assert.

• gh-100690: Mock objects which are not unsafe will now raise an AttributeError when accessing an attribute that matches the name of an assertion but without the prefix assert_, e.g. accessing called_once instead of assert_called_once. This is in addition to this already happening for accessing attributes with prefixes assert, assret, asert, aseert, and assrt.

• gh-96127: inspect.signature was raising TypeError on call with mock objects. Now it correctly returns (*args, **kwargs) as infered signature.

5.0.0

• 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 a create_autospec(...) call. 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-45156: Fixes infinite loop on :func:unittest.mock.seal of mocks created by :func:~unittest.create_autospec.

• bpo-41403: Make :meth:mock.patch raise a :exc:TypeError with a relevant 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.

... (truncated)

Commits

• 03a3f12 Preparing for 5.0.2 release.
• b8a7ded latest sync point
• 079655c gh-102978: Fix mock.patch function signatures for class and staticmethod deco...
• 1c7bfef gh-103329: Add regression test for PropertyMock with side effect (#103358)
• 09b0b29 correct lastsync.txt revision
• 4145e0f Additionally test on pypy 3.9 / 7.3.11
• e132217 Actually use pypy to run pypy's CI
• 921fad1 Preparing for 5.0.1 release.
• 696fb23 Backwards compatibility fix for 3.7 and earlier.
• 296d856 latest sync point
• 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)

[jbnable]

Checkmarx One – Scan Summary & Details – f8250ad9-bd61-486a-9b01-d6d41dabc929

No New Or Fixed Issues Found

[dependabot[bot]]

Superseded by #500.