Bump pytest-mock from 3.1.0 to 3.6.1

[dependabot]

Bumps pytest-mock from 3.1.0 to 3.6.1.

Release notes

Sourced from pytest-mock's releases.

3.3.1 (2020-08-24)

• Introduce MockFixture as an alias to MockerFixture.

  Before 3.3.0, the fixture class was named MockFixture, but was renamed to MockerFixture to better match the mocker fixture. While not officially part of the API, it was later discovered that this broke the code of some users which already imported pytest_mock.MockFixture for type annotations, so we decided to reintroduce the name as an alias.

  Note however that this is just a stop gap measure, and new code should use MockerFixture for type annotations.

• Improved typing for MockerFixture.patch (#201). Thanks @​srittau for the PR.

3.3.0 (2020-08-21)

• pytest-mock now includes inline type annotations and exposes them to user programs. The mocker fixture returns pytest_mock.MockerFixture, which can be used to annotate your tests:

  from pytest_mock import MockerFixture
  def test_foo(mocker: MockerFixture) -> None:
  ...

  The type annotations were developed against mypy version 0.782, the minimum version supported at the moment. If you run into an error that you believe to be incorrect, please open an issue.

  Many thanks to @​staticdev for providing the initial patch #199.

3.2.0 (2020-07-11)

• AsyncMock is now exposed in mocker and supports provides assertion introspection similar to Mock objects.

  Added by @​tirkarthi in #197.

3.1.1 (2020-05-31)

• Fixed performance regression caused by the ValueError raised when mocker is used as context manager (#191).

Changelog

Sourced from pytest-mock's changelog.

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.

.. _@​iforapsy: https://github.com/iforapsy .. _#221: pytest-dev/pytest-mock#221

3.4.0 (2020-12-15)

... (truncated)

Commits

• 6730ce3 Release 3.6.1
• b4d91e0 modify resetall to work with patch object (#241)
• c387818 Merge pull request #239 from pytest-dev/pre-commit-ci-update-config
• 278a23d [pre-commit.ci] pre-commit autoupdate
• 033f2f5 Merge pull request #238 from pytest-dev/pre-commit-ci-update-config
• f830bb9 [pre-commit.ci] pre-commit autoupdate
• 3a4b13b Remove requirements section from README
• 4803269 Merge pull request #236 from nicoddemus/release-3.6.0
• 4716752 Drop Python 3.5 support
• 3425616 Move setup.cfg to mypy.ini
• 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]

The following labels could not be found: dependencies, autosquash.

[dependabot]

Superseded by #198.