Bump pytest-mock from 3.3.1 to 3.7.0

[dependabot[bot]]

Bumps pytest-mock from 3.3.1 to 3.7.0.

Release notes

Sourced from pytest-mock's releases.

3.7.0

• Python 3.10 now officially supported.
• Dropped support for Python 3.6.

3.6.1 (2021-05-06)

• Fix mocker.resetall() when using mocker.spy() (#237). Thanks @​blaxter for the report and @​shadycuz for the PR.

3.6.0 (2021-04-24)

• pytest-mock no longer supports Python 3.5.
• Correct type annotations for mocker.patch.object to also include the string form. Thanks @​plannigan for the PR (#235).
• reset_all now supports return_value and side_effect keyword arguments. Thanks @​alex-marty for the PR (#214).

3.5.1 (2021-01-10)

• Use inspect.getattr_static instead of resorting to object.__getattribute__ magic. This should better comply with objects which implement a custom descriptor protocol. Thanks @​yesthesoup for the PR (#224).

3.5.0 (2021-01-04)

• Now all patch functions will emit a warning instead of raising a ValueError when used as a context-manager. Thanks @​iforapsy for the PR (#221).
• Additionally, mocker.patch.context_manager is available when the user intends to mock a context manager (for example threading.Lock object), which will not emit that warning.

3.4.0 (2020-12-15)

• Add [mock.seal]{.title-ref} alias to the [mocker]{.title-ref} fixture (#211). Thanks @​coiax for the PR.

• Fixed spying on exceptions not covered by the Exception superclass (#215), like KeyboardInterrupt -- PR #216 by @​webknjaz.

  Before the fix, both spy_return and spy_exception were always assigned to None whenever such an exception happened. And after this fix, spy_exception is set to a correct value of an exception

Changelog

Sourced from pytest-mock's changelog.

3.7.0 (2022-01-28)

• Python 3.10 now officially supported.
• Dropped support for Python 3.6.

3.6.1 (2021-05-06)

• Fix mocker.resetall() when using mocker.spy() ([#237](https://github.com/pytest-dev/pytest-mock/issues/237)). Thanks @blaxter for the report and @shadycuz_ for the PR.

.. _@​blaxter: https://github.com/blaxter .. _@​shadycuz: https://github.com/shadycuz .. _#237: pytest-dev/pytest-mock#237

3.6.0 (2021-04-24)

• pytest-mock no longer supports Python 3.5.

• Correct type annotations for mocker.patch.object to also include the string form. Thanks @plannigan_ for the PR ([#235](https://github.com/pytest-dev/pytest-mock/issues/235)_).

• reset_all now supports return_value and side_effect keyword arguments. Thanks @alex-marty_ for the PR ([#214](https://github.com/pytest-dev/pytest-mock/issues/214)_).

.. _@​alex-marty: https://github.com/alex-marty .. _@​plannigan: https://github.com/plannigan .. _#214: pytest-dev/pytest-mock#214 .. _#235: pytest-dev/pytest-mock#235

3.5.1 (2021-01-10)

• Use inspect.getattr_static instead of resorting to object.__getattribute__ magic. This should better comply with objects which implement a custom descriptor protocol. Thanks @yesthesoup_ for the PR ([#224](https://github.com/pytest-dev/pytest-mock/issues/224)_).

.. _@​yesthesoup: https://github.com/yesthesoup .. _#224: pytest-dev/pytest-mock#224

3.5.0 (2021-01-04)

• Now all patch functions will emit a warning instead of raising a ValueError when used as a context-manager. Thanks @iforapsy_ for the PR ([#221](https://github.com/pytest-dev/pytest-mock/issues/221)_).

• Additionally, mocker.patch.context_manager is available when the user intends to mock a context manager (for example threading.Lock object), which will not emit that warning.

... (truncated)

Commits

• 3c6b070 Remove obsolete tox envs
• 5947b5a Release 3.7.0
• f128a23 Merge pull request #273 from nicoddemus/asyncio-272
• cb4d567 Drop Python 3.6, add support for 3.10
• 0b869db Configure asyncio_mode to fix tests
• 3ca933a Merge pull request #269 from pytest-dev/pre-commit-ci-update-config
• 2bf7b61 [pre-commit.ci] pre-commit autoupdate
• 2d411f8 Merge pull request #267 from pytest-dev/pre-commit-ci-update-config
• 83c7468 [pre-commit.ci] pre-commit autoupdate
• 3256ac0 Merge pull request #266 from pytest-dev/pre-commit-ci-update-config
• 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'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

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