3.6.1 (2021-05-06)
------------------
* Fix ``mocker.resetall()`` when using ``mocker.spy()``
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.
* ``reset_all`` now supports ``return_value`` and ``side_effect`` keyword arguments.
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.
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.
* 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` alias to the `mocker` fixture.
* Fixed spying on exceptions not covered by the ``Exception``
superclass, like ``KeyboardInterrupt``.
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
that has actually happened.
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``
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:
.. code-block:: python
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.
3.2.0 (2020-07-11)
------------------
* `AsyncMock <https://docs.python.org/3/library/unittest.mock.html#unittest.mock.AsyncMock>`__ is now exposed in ``mocker`` and supports provides assertion introspection similar to ``Mock`` objects.
3.1.1 (2020-05-31)
------------------
* Fixed performance regression caused by the ``ValueError`` raised
when ``mocker`` is used as context manager.
3.1.0 (2020-04-18)
------------------
* New mocker fixtures added that allow using mocking functionality in other scopes:
* ``class_mocker``
* ``module_mocker``
* ``package_mocker``
* ``session_mocker``
3.0.0 (2020-03-31)
------------------
* 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.
a08fca3ff1