Changelog
### 3.0.0
```
------------------
* Python 2.7 and 3.4 are no longer supported. Users using ``pip 9`` or later will install
a compatible version automatically.
* ``mocker.spy`` now also works with ``async def`` functions (`179`_). Thanks `frankie567`_ for the PR!
.. _179: https://github.com/pytest-dev/pytest-mock/issues/179
.. _frankie567: https://github.com/frankie567
```
### 2.0.0
```
------------------
Breaking Changes
++++++++++++++++
* ``mocker.spy`` attributes for tracking returned values and raised exceptions of its spied functions
are now called ``spy_return`` and ``spy_exception``, instead of reusing the existing
``MagicMock`` attributes ``return_value`` and ``side_effect``.
Version ``1.13`` introduced a serious regression: after a spied function using ``mocker.spy``
raises an exception, further calls to the spy will not call the spied function,
always raising the first exception instead: assigning to ``side_effect`` causes
``unittest.mock`` to behave this way (`175`_).
* The deprecated ``mock`` alias to the ``mocker`` fixture has finally been removed.
.. _175: https://github.com/pytest-dev/pytest-mock/issues/175
```
### 1.13.0
```
-------------------
* The object returned by ``mocker.spy`` now also tracks any side effect
of the spied method/function.
```
### 1.12.1
```
-------------------
* Fix error if ``mocker.patch`` is used in code where the source file
is not available, for example stale ``.pyc`` files (`169`_).
.. _169: https://github.com/pytest-dev/pytest-mock/issues/169issuecomment-555729265
```
### 1.12.0
```
-------------------
* Now all patch functions also raise a ``ValueError`` when used
as a context-manager. Thanks `AlexGascon`_ for the PR (`168`_).
.. _AlexGascon: https://github.com/AlexGascon
.. _168: https://github.com/pytest-dev/pytest-mock/pull/168
```
### 1.11.2
```
-------------------
* The *pytest introspection follows* message is no longer shown
if there is no pytest introspection (`154`_).
Thanks `The-Compiler`_ for the report.
* ``mocker`` now raises a ``ValueError`` when used as a context-manager.
Thanks `binarymason`_ for the PR (`165`_).
.. _154: https://github.com/pytest-dev/pytest-mock/issues/154
.. _165: https://github.com/pytest-dev/pytest-mock/pull/165
.. _binarymason: https://github.com/binarymason
```
### 1.11.1
```
-------------------
* Fix ``mocker.spy`` on Python 2 when used on non-function objects
which implement ``__call__`` (`157`_). Thanks `pbasista`_ for
the report.
.. _157: https://github.com/pytest-dev/pytest-mock/issues/157
.. _pbasista: https://github.com/pbasista
```
Links
- PyPI: https://pypi.org/project/pytest-mock
- Changelog: https://pyup.io/changelogs/pytest-mock/
- Repo: https://github.com/pytest-dev/pytest-mock/
pyup-bot
commented
4 years ago
This PR updates pytest-mock from 1.11.0 to 3.0.0.
Changelog
### 3.0.0 ``` ------------------ * Python 2.7 and 3.4 are no longer supported. Users using ``pip 9`` or later will install a compatible version automatically. * ``mocker.spy`` now also works with ``async def`` functions (`179`_). Thanks `frankie567`_ for the PR! .. _179: https://github.com/pytest-dev/pytest-mock/issues/179 .. _frankie567: https://github.com/frankie567 ``` ### 2.0.0 ``` ------------------ Breaking Changes ++++++++++++++++ * ``mocker.spy`` attributes for tracking returned values and raised exceptions of its spied functions are now called ``spy_return`` and ``spy_exception``, instead of reusing the existing ``MagicMock`` attributes ``return_value`` and ``side_effect``. Version ``1.13`` introduced a serious regression: after a spied function using ``mocker.spy`` raises an exception, further calls to the spy will not call the spied function, always raising the first exception instead: assigning to ``side_effect`` causes ``unittest.mock`` to behave this way (`175`_). * The deprecated ``mock`` alias to the ``mocker`` fixture has finally been removed. .. _175: https://github.com/pytest-dev/pytest-mock/issues/175 ``` ### 1.13.0 ``` ------------------- * The object returned by ``mocker.spy`` now also tracks any side effect of the spied method/function. ``` ### 1.12.1 ``` ------------------- * Fix error if ``mocker.patch`` is used in code where the source file is not available, for example stale ``.pyc`` files (`169`_). .. _169: https://github.com/pytest-dev/pytest-mock/issues/169issuecomment-555729265 ``` ### 1.12.0 ``` ------------------- * Now all patch functions also raise a ``ValueError`` when used as a context-manager. Thanks `AlexGascon`_ for the PR (`168`_). .. _AlexGascon: https://github.com/AlexGascon .. _168: https://github.com/pytest-dev/pytest-mock/pull/168 ``` ### 1.11.2 ``` ------------------- * The *pytest introspection follows* message is no longer shown if there is no pytest introspection (`154`_). Thanks `The-Compiler`_ for the report. * ``mocker`` now raises a ``ValueError`` when used as a context-manager. Thanks `binarymason`_ for the PR (`165`_). .. _154: https://github.com/pytest-dev/pytest-mock/issues/154 .. _165: https://github.com/pytest-dev/pytest-mock/pull/165 .. _binarymason: https://github.com/binarymason ``` ### 1.11.1 ``` ------------------- * Fix ``mocker.spy`` on Python 2 when used on non-function objects which implement ``__call__`` (`157`_). Thanks `pbasista`_ for the report. .. _157: https://github.com/pytest-dev/pytest-mock/issues/157 .. _pbasista: https://github.com/pbasista ```Links
- PyPI: https://pypi.org/project/pytest-mock - Changelog: https://pyup.io/changelogs/pytest-mock/ - Repo: https://github.com/pytest-dev/pytest-mock/