Log message:
py-test-mock: updated to 3.14.0

3.14.0 (2024-03-21)
-------------------

* `MockType`` and ``AsyncMockType`` can be imported from ``pytest_mock`` for \ 
type annotation purposes.

* Fixed a regression which would cause ``mocker.patch.object`` to not being \ 
properly cleared between tests.

3.13.0 (2024-03-21)
-------------------

* ``spy`` now has ``spy_return_list``, which is a list containing all the values \ 
returned by the spied function.
* ``pytest-mock`` now requires ``pytest>=6.2.5``.
* pytest-mock's ``setup.py`` file is removed.
  If you relied on this file, e.g. to install pytest using ``setup.py install``,
  please see `Why you shouldn't invoke setup.py directly \ 
<https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html#summary>`_ \ 
for alternatives.

Log message:
py-test-mock: updated to 3.12.0

3.12.0 (2023-10-19)
-------------------

* Added support for Python 3.12.
* Dropped support for EOL Python 3.7.
* ``mocker.resetall()`` now also resets mocks created by ``mocker.create_autospec``

Log message:
py-test-mock: updated to 3.11.1

3.11.1 (2023-06-15)
-------------------
* Fixed introspection for failed ``assert_has_calls``
* Updated type annotations for ``mocker.patch`` and ``mocker.spy``

Log message:
Mass-change BUILD_DEPENDS to TOOL_DEPENDS outside mk/.

Almost all uses, if not all of them, are wrong, according to the
semantics of BUILD_DEPENDS (packages built for target available for
use _by_ tools at build-time) and TOOL_DEPEPNDS (packages built for
host available for use _as_ tools at build-time).

No change to BUILD_DEPENDS as used correctly inside buildlink3.

As proposed on tech-pkg:
https://mail-index.netbsd.org/tech-pkg/2023/06/03/msg027632.html

Log message:
py-test-mock: updated to 3.10.0

3.10.0 (2022-10-05)
* Added new ``mocker.stop(m)`` method to stop specific ``mocker.patch`` or \ 
``mocker.spy`` calls.

3.9.0 (2022-09-28)
* Expose ``NonCallableMagicMock`` via the ``mocker`` fixture.

3.8.2 (2022-07-05)
- Fixed ``AsyncMock`` support for Python 3.7+ in ``mocker.async_stub``.

3.8.1 (2022-06-24)
* Fixed regression caused by an explicit ``mock`` dependency in the code.

3.8.0 (2022-06-24)
* Add ``MockerFixture.async_mock`` method.

Log message:
py-test-mock: updated to 3.7.0

3.7.0 (2022-01-28)
------------------
* Python 3.10 now officially supported.
* Dropped support for Python 3.6.

Log message:
*: bump PKGREVISION for egg.mk users

They now have a tool dependency on py-setuptools instead of a DEPENDS

Log message:
py-test-mock: updated to 3.6.1

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.