Bump pytest-mock from 3.4.0 to 3.6.1
Bumps pytest-mock from 3.4.0 to 3.6.1.
Release notes
Sourced from pytest-mock's releases.
3.6.1 (2021-05-06)
- Fix
mocker.resetall()when usingmocker.spy()(#237). Thanks@blaxterfor the report and@shadycuzfor the PR.3.6.0 (2021-04-24)
- pytest-mock no longer supports Python 3.5.
- Correct type annotations for
mocker.patch.objectto also include the string form. Thanks@planniganfor the PR (#235).reset_allnow supportsreturn_valueandside_effectkeyword arguments. Thanks@alex-martyfor the PR (#214).3.5.1 (2021-01-10)
- Use
inspect.getattr_staticinstead of resorting toobject.__getattribute__magic. This should better comply with objects which implement a custom descriptor protocol. Thanks@yesthesoupfor the PR (#224).3.5.0 (2021-01-04)
- Now all patch functions will emit a warning instead of raising a
ValueErrorwhen used as a context-manager. Thanks@iforapsyfor the PR (#221).- Additionally,
mocker.patch.context_manageris available when the user intends to mock a context manager (for examplethreading.Lockobject), which will not emit that warning.
Changelog
Sourced from pytest-mock's changelog.
3.6.1 (2021-05-06)
- Fix
mocker.resetall()when usingmocker.spy()([#237](https://github.com/pytest-dev/pytest-mock/issues/237)). Thanks@blaxterfor the report and@shadycuz_ for the PR... _
@blaxter: https://github.com/blaxter .. _@shadycuz: https://github.com/shadycuz .. _#237: pytest-dev/pytest-mock#2373.6.0 (2021-04-24)
pytest-mock no longer supports Python 3.5.
Correct type annotations for
mocker.patch.objectto also include the string form. Thanks@plannigan_ for the PR ([#235](https://github.com/pytest-dev/pytest-mock/issues/235)_).
reset_allnow supportsreturn_valueandside_effectkeyword 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#2353.5.1 (2021-01-10)
- Use
inspect.getattr_staticinstead of resorting toobject.__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#2243.5.0 (2021-01-04)
Now all patch functions will emit a warning instead of raising a
ValueErrorwhen used as a context-manager. Thanks@iforapsy_ for the PR ([#221](https://github.com/pytest-dev/pytest-mock/issues/221)_).Additionally,
mocker.patch.context_manageris available when the user intends to mock a context manager (for examplethreading.Lockobject), which will not emit that warning... _
@iforapsy: https://github.com/iforapsy .. _#221: pytest-dev/pytest-mock#221
Commits
6730ce3Release 3.6.1b4d91e0modify resetall to work with patch object (#241)c387818Merge pull request #239 from pytest-dev/pre-commit-ci-update-config278a23d[pre-commit.ci] pre-commit autoupdate033f2f5Merge pull request #238 from pytest-dev/pre-commit-ci-update-configf830bb9[pre-commit.ci] pre-commit autoupdate3a4b13bRemove requirements section from README4803269Merge pull request #236 from nicoddemus/release-3.6.04716752Drop Python 3.5 support3425616Move 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)