Scheduled weekly dependency update for week 32

[pyup-bot]

Update pytest from 9.0.3 to 9.1.1.

Changelog

9.1.1

=========================

Bug fixes
---------

- `14220 <https://github.com/pytest-dev/pytest/issues/14220>`_: Fixed a logic bug in :class:`pytest.RaisesGroup` which would might cause it to display incorrect "It matches `FooError()` which was paired with `BarError`" messages.


- `14591 <https://github.com/pytest-dev/pytest/issues/14591>`_: Fixed a regression in pytest 9.1.0 which caused overriding a parametrized fixture with an indirect `pytest.mark.parametrize` to fail with "duplicate parametrization of '<fixture name>'".


- `14606 <https://github.com/pytest-dev/pytest/issues/14606>`_: Fixed ``list-item`` typing errors from mypy in :ref:`pytest.mark.parametrize <pytest.mark.parametrize ref>` ``argvalues`` parameter.


- `14608 <https://github.com/pytest-dev/pytest/issues/14608>`_: Fixed a regression in pytest 9.1.0 where ``conftest.py`` files located in ``<invocation dir>/test*`` were no longer loaded as initial conftests when invoked without arguments.
This could cause certain hooks (like :hook:`pytest_addoption`) in these files to not fire.

9.1.0

=========================

Removals and backward incompatible breaking changes
---------------------------------------------------

- `14533 <https://github.com/pytest-dev/pytest/issues/14533>`_: When using :option:`--doctest-modules`, autouse fixtures with ``module``, ``package`` or ``session`` scope that are defined inline in Python test modules (not plugins or conftests) will now possibly execute twice.

If this is undesirable, move the fixture definition to a ``conftest.py`` file if possible.

Technical explanation for those interested:
When using `--doctest-modules`, pytest possibly collects Python modules twice, once as :class:`pytest.Module` and once as a ``DoctestModule`` (depending on the configuration).
Due to improvements in pytest's fixture implementation, if e.g. the ``DoctestModule`` collects a fixture, it is now visible to it only, and not to the ``Module``.
This means that both need to register the fixtures independently.



Deprecations (removal in next major release)
--------------------------------------------

- `10819 <https://github.com/pytest-dev/pytest/issues/10819>`_: Added a deprecation warning for class-scoped fixtures defined as instance methods (without ``classmethod``). Such fixtures set attributes on a different instance than the test methods use, leading to unexpected behavior. Use ``classmethod`` decorator instead -- by :user:`yastcher`.

See :issue:`10819` and :issue:`14011`.


- `12882 <https://github.com/pytest-dev/pytest/issues/12882>`_: Calling :meth:`request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue>` during teardown to request a fixture that was not already requested is now deprecated and will become an error in pytest 10.

See :ref:`dynamic-fixture-request-during-teardown` for details.


- `13409 <https://github.com/pytest-dev/pytest/issues/13409>`_: Using non-:class:`~collections.abc.Collection` iterables (such as generators, iterators, or custom iterable objects) for the ``argvalues`` parameter in :ref:`pytest.mark.parametrize <pytest.mark.parametrize ref>` and :meth:`metafunc.parametrize <pytest.Metafunc.parametrize>` is now deprecated.

These iterables get exhausted after the first iteration,
leading to tests getting unexpectedly skipped in cases such as running :func:`pytest.main()` multiple times,
using class-level parametrize decorators,
or collecting tests multiple times.

See :ref:`parametrize-iterators` for details and suggestions.


- `13946 <https://github.com/pytest-dev/pytest/issues/13946>`_: The private ``config.inicfg`` attribute is now deprecated.
Use :meth:`config.getini() <pytest.Config.getini>` to access configuration values instead.

See :ref:`config-inicfg` for more details.


- `14004 <https://github.com/pytest-dev/pytest/issues/14004>`_: Passing ``baseid`` to :class:`~pytest.FixtureDef` or ``nodeid`` strings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins.

Use the ``node`` parameter instead for fixture scoping. This enables more robust node-based
matching instead of string prefix matching.
If you've used ``nodeid=None``, pass ``node=session`` instead.

This will be removed in pytest 10.


- `14335 <https://github.com/pytest-dev/pytest/issues/14335>`_: The method of configuring hooks using markers, deprecated since pytest 7.2, is now scheduled to be removed in pytest 10.
See :ref:`hook-markers` for more details.


- `14434 <https://github.com/pytest-dev/pytest/issues/14434>`_: The :option:`--pastebin` option is now deprecated.
The same functionality is now available in an external plugin, :pypi:`pytest-pastebin`.
See :ref:`pastebin-deprecated` for more details.


- `14513 <https://github.com/pytest-dev/pytest/issues/14513>`_: The private ``FixtureDef.has_location`` attribute is now deprecated and will be removed in pytest 10.
See :ref:`fixturedef-has-location-deprecated` for details.


- `1764 <https://github.com/pytest-dev/pytest/issues/1764>`_: :func:`pytest.console_main` is now deprecated and will be removed in pytest 10.
It was never intended for programmatic use; use :func:`pytest.main` instead.



New features
------------

- `12376 <https://github.com/pytest-dev/pytest/issues/12376>`_: Added :func:`pytest.register_fixture()` to register fixtures using an imperative interface.

This is an advanced function intended for use by plugins.

Normally, fixtures should be registered declaratively using the :func:`pytest.fixture <pytest.fixture>` decorator.
Pytest looks for these fixture definitions during the collection phase and registers them automatically.
For some plugin usecases the declarative interface can be cumbersome or unviable, in which case this imperative interface can be used.


- `14023 <https://github.com/pytest-dev/pytest/issues/14023>`_: Added `--report-chars` long CLI option.


- `14371 <https://github.com/pytest-dev/pytest/issues/14371>`_: Added :option:`--max-warnings` command-line option and :confval:`max_warnings` configuration option to fail the test run when the number of warnings exceeds a given threshold -- by :user:`miketheman`.


- `6757 <https://github.com/pytest-dev/pytest/issues/6757>`_: Added the :confval:`assertion_text_diff_style` configuration option, allowing
string equality failures to be rendered as separate ``Left:`` and ``Right:``
blocks instead of ``ndiff`` output.


- `8395 <https://github.com/pytest-dev/pytest/issues/8395>`_: Added support for :class:`~datetime.datetime` and :class:`~datetime.timedelta` comparisons with :func:`pytest.approx`. An explicit ``abs`` or ``rel`` tolerance as a :class:`~datetime.timedelta` is required and relative tolerance is not supported for datetime comparisons -- by :user:`hamza-mobeen`.



Improvements in existing functionality
--------------------------------------

- `11225 <https://github.com/pytest-dev/pytest/issues/11225>`_: :func:`pytest.warns` now shows "Regex pattern did not match" instead of "DID NOT WARN" when warnings were emitted but the ``match`` pattern did not match.


- `11295 <https://github.com/pytest-dev/pytest/issues/11295>`_: Improved output of ``--fixtures-per-test`` by excluding internal-implementation fixtures generated by ``pytest.mark.parametrize`` and similar.


- `13241 <https://github.com/pytest-dev/pytest/issues/13241>`_: :func:`pytest.raises`, :func:`pytest.warns` and :func:`pytest.deprecated_call` now uses :class:`ParamSpec` for the type hint to the (old and not recommended) callable overload, instead of :class:`Any`. This allows type checkers to raise errors when passing incorrect function parameters.
``func`` can now also be passed as a kwarg, which the type hint previously showed as possible but didn't accept.


- `13862 <https://github.com/pytest-dev/pytest/issues/13862>`_: Improved the readability of "DID NOT RAISE" error messages by using the exception type's name instead of its `repr`.


- `14026 <https://github.com/pytest-dev/pytest/issues/14026>`_: Added test coverage for compiled regex patterns in :func:`pytest.raises` match parameter.


- `14137 <https://github.com/pytest-dev/pytest/issues/14137>`_: `pytest.ScopeName` is now public to allow using it in function signatures.


- `14342 <https://github.com/pytest-dev/pytest/issues/14342>`_: Marked ``yield_fixture`` as deprecated to type checkers using the ``deprecated`` decorator. Note it
:ref:`has originally been deprecated <yield-fixture-deprecated>` in pytest 6.2 already.


- `14373 <https://github.com/pytest-dev/pytest/issues/14373>`_: Added type annotations for :func:`pytest.approx`.


- `14430 <https://github.com/pytest-dev/pytest/issues/14430>`_: When using ``--setup-show``, a space is now printed after the test name (and possibly used fixtures), to separate it from the test result.


- `14441 <https://github.com/pytest-dev/pytest/issues/14441>`_: Reduced the default number of ``gc.collect()`` passes in the ``unraisableexception`` plugin from 5 to 1 on CPython, where reference counting makes a single pass sufficient. PyPy retains 5 passes due to object resurrection via ``__del__``. This can noticeably speed up test suites that trigger many pytester runs.


- `14461 <https://github.com/pytest-dev/pytest/issues/14461>`_: Improved assertion failure explanations for equality comparisons between mapping objects that are not ``dict`` instances.


- `14513 <https://github.com/pytest-dev/pytest/issues/14513>`_: The order in which fixture definitions overriding each other are resolved is now determined first by their *visibility* in the collection tree rather than by the order in which they are registered.

A fixture defined for a more specific node (e.g. a module or an item) now always takes precedence over one with the same name defined for a more general node (e.g. the session), even when the more general one was registered later.
Fixtures with non-comparable visibility or the same visibility keep the existing behavior of "last registered wins".
This change is supposed to only affect plugins which register multiple fixtures programmatically with the same name.


- `14524 <https://github.com/pytest-dev/pytest/issues/14524>`_: Add official Python 3.15 support.


- `1764 <https://github.com/pytest-dev/pytest/issues/1764>`_: Improved argparse program name to show ``pytest``, ``python -m pytest``, or ``pytest.main()`` based on how pytest was invoked, making help and error messages clearer.


- `8265 <https://github.com/pytest-dev/pytest/issues/8265>`_: Emit a ``PytestCollectionWarning`` when a module-level ``__getattr__`` returns ``None`` for ``pytestmark`` instead of raising ``AttributeError``.

Previously this caused a cryptic ``TypeError: got None instead of Mark`` error.
Now pytest issues a helpful warning and continues collecting the module normally.



Bug fixes
---------

- `13192 <https://github.com/pytest-dev/pytest/issues/13192>`_: Fixed `|` (pipe) not being treated as a regex meta-character that needs escaping in :func:`pytest.raises(match=...) <pytest.raises>`.


- `13484 <https://github.com/pytest-dev/pytest/issues/13484>`_: Fixed ``-W`` option values being duplicated in ``Config.known_args_namespace``.


- `13626 <https://github.com/pytest-dev/pytest/issues/13626>`_: Fixed function-scoped fixture values being kept alive after a test was interrupted by ``KeyboardInterrupt`` or early exit,
allowing them to potentially be released more promptly.


- `13784 <https://github.com/pytest-dev/pytest/issues/13784>`_: Fixed ``capteesys`` producing doubled output when used with ``--capture=no`` (``-s``).


- `13817 <https://github.com/pytest-dev/pytest/issues/13817>`_: Fixed a secondary `AttributeError` masking the original error when an option argument fails to initialize.


- `13884 <https://github.com/pytest-dev/pytest/issues/13884>`_: Fixed rare internal IndexError caused by `builtins.compile` being overridden in client code.


- `13885 <https://github.com/pytest-dev/pytest/issues/13885>`_: Fixed autouse fixtures defined inside a :class:`unittest.TestCase` class running even when the class is decorated with :func:`unittest.skip` or :func:`unittest.skipIf` -- regression since pytest 8.1.0.


- `13917 <https://github.com/pytest-dev/pytest/issues/13917>`_: :class:`unittest.SkipTest` is no longer considered an interactive exception, i.e. :hook:`pytest_exception_interact` is no longer called for it.


- `13963 <https://github.com/pytest-dev/pytest/issues/13963>`_: Fixed subtests running with :pypi:`pytest-xdist` when their contexts contain objects that are not JSON-serializable.

Fixes `pytest-dev/pytest-xdist1273 <https://github.com/pytest-dev/pytest-xdist/issues/1273>`__.


- `14004 <https://github.com/pytest-dev/pytest/issues/14004>`_: Fixed conftest.py fixture scoping when :confval:`testpaths` points outside of the :ref:`rootdir <rootdir>`.

Previously, fixtures from nested conftest.py files would incorrectly leak to sibling directories
when using a relative ``testpaths`` like ``../tests/sdk``.

Conftest fixtures are now parsed during :class:`Directory <pytest.Directory>` collection, using the ``Directory`` node for proper scoping.


- `14050 <https://github.com/pytest-dev/pytest/issues/14050>`_: Display dictionary differences in assertion failures using the original key insertion order instead of sorted order.


- `14080 <https://github.com/pytest-dev/pytest/issues/14080>`_: fix missing type annotations on ``Pytester.makepyfile`` and ``Pytester.maketxtfile`` methods.


- `14114 <https://github.com/pytest-dev/pytest/issues/14114>`_: An exception from :hook:`pytest_fixture_post_finalizer` no longer prevents fixtures from being torn down, causing additional errors in the following tests.


- `14161 <https://github.com/pytest-dev/pytest/issues/14161>`_: Fixed :meth:`monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale entry on the undo stack when the underlying ``setattr()`` call fails (e.g. on immutable targets), causing an ``AttributeError`` crash during teardown.


- `14214 <https://github.com/pytest-dev/pytest/issues/14214>`_: Fixed ``-v`` hint in :func:`pytest.raises` match diff not working because assertion verbosity was not propagated.


- `14234 <https://github.com/pytest-dev/pytest/issues/14234>`_: Allow :ref:`pytest.HIDDEN_PARAM <hidden-param>` in :ref:`pytest.mark.parametrize(ids=...) <pytest.mark.parametrize ref>` typing.


- `14248 <https://github.com/pytest-dev/pytest/issues/14248>`_: Fixed direct parametrization causing the static fixture closure (as reflected in :data:`request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit fixtures that are requested transitively from overridden fixtures.


- `14263 <https://github.com/pytest-dev/pytest/issues/14263>`_: Unraisable exceptions from finalizers are now collected during ``pytest_unconfigure``, before pytest tears down the warning filters installed for the session. Previously the collection ran from a cleanup callback whose order relative to other plugins' cleanups was not guaranteed, so an active ``error`` filter could be removed before the exception surfaced and a late resource leak would pass silently. A ``-W error`` filter, or any filter matching :class:`pytest.PytestUnraisableExceptionWarning`, now promotes these exceptions to failures regardless of plugin cleanup order.


- `14377 <https://github.com/pytest-dev/pytest/issues/14377>`_: Fixed crash in `Config.get_terminal_writer` when an assertion fails with the ``terminalreporter`` plugin disabled.


- `14381 <https://github.com/pytest-dev/pytest/issues/14381>`_: Fixed ``-V`` (short form of ``--version``) to properly display the current version.


- `14389 <https://github.com/pytest-dev/pytest/issues/14389>`_: Improved :func:`pytest.raises(..., match=...) <pytest.raises>` failures to suppress the mismatched exception as a cause of the resulting ``AssertionError``.


- `14392 <https://github.com/pytest-dev/pytest/issues/14392>`_: Fixed a bug in :func:`pytest.raises(match=...) <pytest.raises>` "fully escaped" detection, causing the regex diff display to be shown in some instances when the raw string diff display should be shown instead.


- `14442 <https://github.com/pytest-dev/pytest/issues/14442>`_: Fixed a regression in pytest 9.0 where :option:`--strict-markers` and :option:`--strict-config` specified through :confval:`addopts` were silently ignored.

Note that when targeting pytest >= 9.0, it's nicer to use :confval:`strict_markers` and :confval:`strict_config`, or :ref:`strict mode <strict mode>`.


- `14456 <https://github.com/pytest-dev/pytest/issues/14456>`_: Fixed :func:`pytest.approx` not recognizing types with ``__array_interface__`` as numpy-like arrays.


- `14474 <https://github.com/pytest-dev/pytest/issues/14474>`_: Fixed a regression where ``-k`` and ``-m`` expressions containing both backslash characters in identifiers and string literal arguments would incorrectly raise a ``SyntaxError`` about escaping.


- `14483 <https://github.com/pytest-dev/pytest/issues/14483>`_: Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary plane characters like emoji) in test failure messages. -- by :user:`EternalRights`


- `14492 <https://github.com/pytest-dev/pytest/issues/14492>`_: Fixed ``Code.getargs()`` incorrectly including local variable names in the returned argument tuple for functions with ``*args`` and/or ``**kwargs``. The method was using ``co_flags`` bitmask values (``4`` and ``8``) directly as counts instead of converting them to ``1`` via ``bool()``, and was not accounting for ``co_kwonlyargcount`` when ``var=True``.


- `3697 <https://github.com/pytest-dev/pytest/issues/3697>`_: Logging capture now works for non-propagating loggers.
Previously only logs which reached the root logger were captured.
This includes :fixture:`caplog` and the "Captured log calls" test reporting.


- `3850 <https://github.com/pytest-dev/pytest/issues/3850>`_: Fixed JUnit XML report: the ``tests`` attribute of the ``<testsuite>`` element now always matches the number of ``<testcase>`` elements in the file. In some cases (test passes but fails during teardown) the ``tests`` attribute would report an incorrect number of testcases in the XML file.


- `5848 <https://github.com/pytest-dev/pytest/issues/5848>`_: :hook:`pytest_fixture_post_finalizer` is no longer called extra times for the same fixture teardown in some cases.


- `719 <https://github.com/pytest-dev/pytest/issues/719>`_: Fixed :ref:`pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking single-element tuple values when using a string argnames with a trailing comma (e.g., ``"arg,"``).

The trailing comma form now correctly behaves like the tuple form ``("arg",)``, treating argvalues as a list of tuples to unpack.



Improved documentation
----------------------

- `11022 <https://github.com/pytest-dev/pytest/issues/11022>`_: Document safer alternatives and scope guidance for monkeypatching standard library functions.


- `11307 <https://github.com/pytest-dev/pytest/issues/11307>`_: Document that ``pytest.hookimpl(specname=...)`` only works for function names starting with ``pytest_``.


- `13038 <https://github.com/pytest-dev/pytest/issues/13038>`_: Document that doctests do not support parametrized fixtures, including parametrized autouse fixtures.


- `13155 <https://github.com/pytest-dev/pytest/issues/13155>`_: Clarified how the ``request`` fixture provides indirect parametrization values via ``request.param``.


- `13304 <https://github.com/pytest-dev/pytest/issues/13304>`_: Clarified in the documentation that hook implementations defined in ``conftest.py`` files are not available to other plugins during their ``pytest_addoption()`` execution, as conftest files are discovered and loaded after builtin and third-party plugins have been initialized. However, initial conftest files themselves can implement ``pytest_addoption()`` to add their own command-line options.


- `13902 <https://github.com/pytest-dev/pytest/issues/13902>`_: Clarified how subtest progress markers are shown in the documentation.


- `14012 <https://github.com/pytest-dev/pytest/issues/14012>`_: The :ref:`ini options ref` section of the API Reference now specified the type and default value of every configuration option.


- `14148 <https://github.com/pytest-dev/pytest/issues/14148>`_: Documented a safe ``pytestconfig.cache`` access pattern when the
``cacheprovider`` plugin is disabled.


- `14303 <https://github.com/pytest-dev/pytest/issues/14303>`_: The documentation is now built with Sphinx >= 9.


- `14465 <https://github.com/pytest-dev/pytest/issues/14465>`_: Updated the hooks how-to page to link the ``newhooks.py`` file in ``pytest-xdist`` at tag ``v3.8.0`` instead of an unrelated 2017-era commit under the old layout. Pointing at a tag keeps the example in sync with the version users actually install, while remaining stable when the project's main branch moves on.



Miscellaneous internal changes
------------------------------

- `14582 <https://github.com/pytest-dev/pytest/issues/14582>`_: Improved the recursion traceback test to exercise all requested traceback styles.

Links

• PyPI: https://pypi.org/project/pytest
• Changelog: https://data.safetycli.com/changelogs/pytest/

Update pytest-asyncio from 1.3.0 to 1.4.0.

Changelog

1.4.0

[1.4.0](https://github.com/pytest-dev/pytest-asyncio/tree/1.4.0) - 2026-05-26

Deprecated

-   Overriding the *event_loop_policy* fixture is deprecated. Use the `pytest_asyncio_loop_factories` hook instead. ([1419](https://github.com/pytest-dev/pytest-asyncio/issues/1419))

Added

-   Added the `pytest_asyncio_loop_factories` hook to parametrize asyncio tests with custom event loop factories.

 The hook returns a mapping of factory names to loop factories, and `pytest.mark.asyncio(loop_factories=[...])` selects a subset of configured factories per test. When a single factory is configured, test names are unchanged.

 Synchronous `pytest_asyncio.fixture` functions now see the correct event loop when custom loop factories are configured, even when test code disrupts the current event loop (e.g., via `asyncio.run()` or `asyncio.set_event_loop(None)`). ([1164](https://github.com/pytest-dev/pytest-asyncio/issues/1164))

Changed

-   Improved the readability of the warning message that is displayed when `asyncio_default_fixture_loop_scope` is unset ([1298](https://github.com/pytest-dev/pytest-asyncio/issues/1298))
-   Only import `asyncio.AbstractEventLoopPolicy` for type checking to avoid raising
 a DeprecationWarning. ([1394](https://github.com/pytest-dev/pytest-asyncio/issues/1394))
-   Updated minimum supported pytest version to v8.4.0. ([1397](https://github.com/pytest-dev/pytest-asyncio/issues/1397))

Fixed

-   Fixed a `ResourceWarning: unclosed event loop` warning that could occur when a synchronous test called `asyncio.run()` or otherwise unset the current event loop after pytest-asyncio had run an async test or fixture. ([724](https://github.com/pytest-dev/pytest-asyncio/issues/724))

Notes for Downstream Packagers

-   Added dependency on `sphinx-tabs >= 3.5` to organize documentation examples into tabs. ([1395](https://github.com/pytest-dev/pytest-asyncio/issues/1395))

1.4.0a2

[1.4.0a2](https://github.com/pytest-dev/pytest-asyncio/tree/1.4.0a2) - 2026-05-02

Deprecated

-   Overriding the *event_loop_policy* fixture is deprecated. Use the `pytest_asyncio_loop_factories` hook instead. ([1419](https://github.com/pytest-dev/pytest-asyncio/issues/1419))

Added

-   Added the `pytest_asyncio_loop_factories` hook to parametrize asyncio tests with custom event loop factories.

 The hook returns a mapping of factory names to loop factories, and `pytest.mark.asyncio(loop_factories=[...])` selects a subset of configured factories per test. When a single factory is configured, test names are unchanged on pytest 8.4+.

 Synchronous `pytest_asyncio.fixture` functions now see the correct event loop when custom loop factories are configured, even when test code disrupts the current event loop (e.g., via `asyncio.run()` or `asyncio.set_event_loop(None)`). ([1164](https://github.com/pytest-dev/pytest-asyncio/issues/1164))

Changed

-   Improved the readability of the warning message that is displayed when `asyncio_default_fixture_loop_scope` is unset ([1298](https://github.com/pytest-dev/pytest-asyncio/issues/1298))
-   Only import `asyncio.AbstractEventLoopPolicy` for type checking to avoid raising
 a DeprecationWarning. ([1394](https://github.com/pytest-dev/pytest-asyncio/issues/1394))
-   Updated minimum supported pytest version to v8.4.0. ([1397](https://github.com/pytest-dev/pytest-asyncio/issues/1397))

Fixed

-   Fixed a `ResourceWarning: unclosed event loop` warning that could occur when a synchronous test called `asyncio.run()` or otherwise unset the current event loop after pytest-asyncio had run an async test or fixture. ([724](https://github.com/pytest-dev/pytest-asyncio/issues/724))

Notes for Downstream Packagers

-   Added dependency on `sphinx-tabs >= 3.5` to organize documentation examples into tabs. ([1395](https://github.com/pytest-dev/pytest-asyncio/issues/1395))

1.4.0a1

[1.4.0a1](https://github.com/pytest-dev/pytest-asyncio/tree/1.4.0a1) - 2026-04-15

Added

-   Added the `pytest_asyncio_loop_factories` hook to parametrize asyncio tests with custom event loop factories.

 The hook returns a mapping of factory names to loop factories, and `pytest.mark.asyncio(loop_factories=[...])` selects a subset of configured factories per test. When a single factory is configured, test names are unchanged on pytest 8.4+.

 Synchronous `pytest_asyncio.fixture` functions now see the correct event loop when custom loop factories are configured, even when test code disrupts the current event loop (e.g., via `asyncio.run()` or `asyncio.set_event_loop(None)`). ([1164](https://github.com/pytest-dev/pytest-asyncio/issues/1164))

Changed

-   Improved the readability of the warning message that is displayed when `asyncio_default_fixture_loop_scope` is unset ([1298](https://github.com/pytest-dev/pytest-asyncio/issues/1298))
-   Only import `asyncio.AbstractEventLoopPolicy` for type checking to avoid raising
 a DeprecationWarning. ([1394](https://github.com/pytest-dev/pytest-asyncio/issues/1394))
-   Updated minimum supported pytest version to v8.4.0. ([1397](https://github.com/pytest-dev/pytest-asyncio/issues/1397))

Notes for Downstream Packagers

-   Added dependency on `sphinx-tabs >= 3.5` to organize documentation examples into tabs. ([1395](https://github.com/pytest-dev/pytest-asyncio/issues/1395))

1.4.0a0

[1.4.0a0](https://github.com/pytest-dev/pytest-asyncio/tree/1.4.0a0) - 2026-03-25

Added

-   Added the `pytest_asyncio_loop_factories` hook to parametrize asyncio tests with custom event loop factories.

 The hook now returns a mapping of factory names to loop factories, and `pytest.mark.asyncio(loop_factories=[...])` can be used to select a subset of configured factories per test. ([1164](https://github.com/pytest-dev/pytest-asyncio/issues/1164))

Changed

-   Improved the readability of the warning message that is displayed when `asyncio_default_fixture_loop_scope` is unset ([1298](https://github.com/pytest-dev/pytest-asyncio/issues/1298))

Links

• PyPI: https://pypi.org/project/pytest-asyncio
• Changelog: https://data.safetycli.com/changelogs/pytest-asyncio/

Update markdown from 3.10.2 to 3.10.3.

Changelog

3.10.3

Fixed

* Fix `SetextHeaderProcessor` regex to prevent mixed `=` and `-` chars in setext-style headers (1606).
* Add AI Policy to Contributing Guide.
* Officially document all included extensions as being in maintenance mode.
* Link the Extension API documentation to the API Reference (1612).

Links

• PyPI: https://pypi.org/project/markdown
• Changelog: https://data.safetycli.com/changelogs/markdown/

Update pillow from 12.2.0 to 12.3.0.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

• PyPI: https://pypi.org/project/pillow
• Changelog: https://data.safetycli.com/changelogs/pillow/

Update pyobjc from 12.1 to 12.2.1.

Changelog

12.2.1

--------------

* :issue:`670`: A number of test files were in a directory name
with lower-case letters where upper-case letters should have been
used. This only affects users checking out the repository on
systems with a case-sensitive filesystem.

* :issue:`671`: Fix build error in the Quartz bindings when the SDK
is for macOS 15 or later and the build target is also macOS 15 or later.

* :issue:`659`: Implement basic support for handling Swift classes that
have an Objective-C representation but are not subclasses of NSObject,
as used in the ``Network`` framework.

.. note::

  The ``Network`` framework builds upon grand central dispatch
  (the ``pyobjc-framework-libdispatch`` package), and because of that
  exceptions in callback handlers will cause a hard crash.

12.2

------------

* Update framework bindings for macOS 26.5 SDK

* The following code failed at the last line in previous versions:

.. sourcecode:: python

  class MyObject(NSObject):
      pass

  obj = MyObject()
  obj.alloc = MyObject.alloc
  print(obj.alloc)  Raised AttributeError

* Backward incompatible changes:

``CFBagCreate`` and ``CFBagCreateMutable`` now match the API in Objective-C, that
is, a value for the ``callbacks`` argument must be passed (must be ``kCFTypeBagCallBacks``).

* :issue:`663`: Fix retain count management for the callbacks registered
with :func:`DARegisterDiskEjectApprovalCallback <DiskArbitration.DARegisterDiskEjectApprovalCallback>`,
:func:`DARegisterDiskMountApprovalCallback <DiskArbitration.DARegisterDiskMountApprovalCallback>`, and
:func:`DARegisterDiskUnmountApprovalCallback <DiskArbitration.DARegisterDiskUnmountApprovalCallback>` in
:doc:`DiskArbitration </apinotes/DiskArbitration>` bindings.

* "Hidden" instance methods were not hidden when looking them
up as an attribute on the class, but found an unbound method
as if the method was not hidden.

* "Hidden" instance methods were visible in ``dir(SomeClass)``.

* :issue:`664`: Fix ``anObject.methodForSelector_(some_selector)`` resolving
to a class method IMP when a bound selector object for ``some_selector``
is a class attribute.

* Fixed some memory leaks on unlikely error paths.

* :issue:`637`: ``numbers.Number`` values are proxies as an ``NSNumber`` value.

* :issue:`665`: the ``__new__`` of Objective-C classes now also support keyword
arguments derived from class selectors of the form ``valueWithKey1:key2:`` (with
an arbitrary prefix instead of ``value``).

The following calls are now possible (as examples):

- ``Foundation.NSHost(address="www.python.org")``, returns ``Foundation.NSHost.hostWithAddress_("www.python.org")``.

- ``AppKit.NSImage(systemSymbolName="multiply.circle.fill", accessibilityDescription="multiply icon")``, returns
 ``AppKit.NSColor.colorWithSystemSymbolName_accessibilityDescription_("multiply.circle.fill", "multiply icon")``.

* Add ``NSMutableData.take_bytes`` on Python 3.15 to mirror the new :class:`bytearray` method
of the same name.

* Rewrite the construction of objects representing method and function metadata, this should result in
(slightly) less memory usage.

* This release gets the testsuite for pyobjc-core to a point where there is
comprehensive test coverage for the entire bridge. All extension modules now
have 100% test coverage according to lcov, although with use for exclusion comments
to ignore code blocks that cannot be reached for various reasons (e.g. ``PyDict_New``
can fail, but that only happens when running out of memory and it not preproducable
during testing).

This enables refactoring the code in pyobjc-core with more confidence that this won't
result in unexpected changes in behaviour.

* Fix error message for invalid argument to a callable with a variable length output buffer argument.

* Fix error handlign for incomplete struct encodings.

* Raise better error when specifying a negative array size for (Objective-)C arguments
where the size of a buffer is passed as one of the arguments to a method or function.

A side effect of this is that a number of manual bindings no longer support passing
-1 as the size of a buffer to derive the size from the Python sequence.

* A Python implementation for a method that returns ``void`` and has a single output
parameter used to leak a reference to the return value.

* Fix crash when a Python implementation with a pass-by-reference output argument
or return value returns an Objective-C instance that is no longer referenced in
Python when the function returns, e.g.:

.. sourcecode:: python

  objc.objc_method(signature=b":o^")
  def myOutput_(self, a):
      return (1, NSObject.alloc().init())

* The bridge could pass a null pointer for a function pointer argument
in some (unlikely) edge cases instead of raising an error.

* Fix various crashes related to edge cases in pass-by-reference
argument handling (none of which happen are used in bindings for
Cocoa frameworks)

* Metadata with a tuple as the value for ``c_array_length_in_arg`` for
an output argument is now honored for methods implemented in Python.

* Fix crash when ``c_array_length_in_arg`` metadata refers to
an non-existing argument.

* Fix handling of transient proxy value, such as when Objective-C
calls a Python method when the object is kept alive from Objective-C
(no active reference in Python).

Edge case found while debugging an unexpected crash in the
free-threaded build which uncovered a bug that also affected
the regular build (but was not triggered there in the test suite).

* ``aValue.methodForSelector_`` now works when the selector is implemented
in Python, the result will be the Python callable (not wrapped in an
:type:`objc.IMP` value).

* A small milestone over the last couple of releases is that test coverage
of the C extension in ``pyobjc-core`` is now at 100%, although with a
liberal sprinkling of coverage exclusions for conditions that cannot
be triggered during testing (such as memory errors).

This makes it possible to refactor parts of this extension module with
more confidence, and has fixed a number of issues in edge conditions.

* :issue:`644`: A number of constants in the CoreAudio bindings evaluated
to byte strings, while the framework expects regular strings.

* :class:`Foundation.NSDecimalNumber` can no longer be subclassed in Python.

Subclasses was possible in older versions, but this is something that
isn't supported in Objective-C and has unexpected behaviour.

* The ``cobject`` and ``c_void_p`` arguments for opaque pointer types
and :class:`objc.objc_object` are now keyword only.

This should not affect user code because passing these values by
value isn't useful (esp. because the ``c_void_p`` argument is the only
one that's useful for interop with 3th-party code).

* :issue:`668`: "frozendict" is supported with Python 3.15a7 and later.

- Instances roundtrip to Objective-C objects similarly as the ``dict`` type,
 including for keyed archiving. For non-keyed archiving a ``frozendict`` value
 is read back as a plain ``dict``.

- The ``__metadata__`` method on :class:`objc.function`, :class:`objc.selector`,
 and :class:`objc.IMP` now returns a ``frozendict`` instead of a regular dict
 to indicate that changing the value has no effect.

* :issue:`674`: Drop GIL when sending KVO notifications

PR by github user `Tim Clem <https://github.com/misterfifths>`_.

* :issue:`669`: Drop dependency on :func:`dis.dis`

PR by github user `Max Bélanger <https://github.com/maxbelanger>`_.

Links

• PyPI: https://pypi.org/project/pyobjc
• Changelog: https://data.safetycli.com/changelogs/pyobjc/
• Repo: https://github.com/ronaldoussoren/pyobjc

Update uharfbuzz from 0.54.1 to 0.56.0.

Changelog

0.56.0

What's Changed
* Publish Pyodide wheels to PyPI (PEP 783) by anthrotype in https://github.com/harfbuzz/uharfbuzz/pull/305
* Update to HarfBuzz 14.3.0 by khaledhosny in https://github.com/harfbuzz/uharfbuzz/pull/308
* Bind fill-glyph paint API by khaledhosny in https://github.com/harfbuzz/uharfbuzz/pull/309
* Bind new SubsetFlags by khaledhosny in https://github.com/harfbuzz/uharfbuzz/pull/310


**Full Changelog**: https://github.com/harfbuzz/uharfbuzz/compare/v0.55.0...v0.56.0

0.56.0b1

What's Changed
* Publish Pyodide wheels to PyPI (PEP 783) by anthrotype in https://github.com/harfbuzz/uharfbuzz/pull/305


**Full Changelog**: https://github.com/harfbuzz/uharfbuzz/compare/v0.55.0...v0.56.0b1

0.55.0

What's Changed
* Bump urllib3 from 2.6.3 to 2.7.0 in /docs by dependabot[bot] in https://github.com/harfbuzz/uharfbuzz/pull/294
* Bump idna from 3.10 to 3.15 in /docs by dependabot[bot] in https://github.com/harfbuzz/uharfbuzz/pull/295
* Warn when using deprecated .create() methods by khaledhosny in https://github.com/harfbuzz/uharfbuzz/pull/296
* Render Sphinx deprecation notice from deprecated decorator by khaledhosny in https://github.com/harfbuzz/uharfbuzz/pull/297
* Fix get_nominal_glyph and get_metric_position return annotations by khaledhosny in https://github.com/harfbuzz/uharfbuzz/pull/299
* Fix get_metric_position_with_fallback to use self by khaledhosny in https://github.com/harfbuzz/uharfbuzz/pull/300
* Fix get_axis_range return annotation by khaledhosny in https://github.com/harfbuzz/uharfbuzz/pull/301
* Update to HarfBuzz 14.2.1 by khaledhosny in https://github.com/harfbuzz/uharfbuzz/pull/302
* Bind hb_face_set_get_table_tags_func() by khaledhosny in https://github.com/harfbuzz/uharfbuzz/pull/298
* Populate API reference  by khaledhosny in https://github.com/harfbuzz/uharfbuzz/pull/303


**Full Changelog**: https://github.com/harfbuzz/uharfbuzz/compare/v0.54.1...v0.55.0

Links

• PyPI: https://pypi.org/project/uharfbuzz
• Changelog: https://data.safetycli.com/changelogs/uharfbuzz/
• Repo: https://github.com/trufont/uharfbuzz

Update ufo2ft from 3.7.3 to 3.9.0.

Changelog

3.9.0

- [outlineCompiler] Building the `glyf` table is now O(n) instead of O(n²) independent of the installed fontTools version (991).
- [filters] Added an `explicitClosingLine` filter to fix interpolatable CFF masters producing mismatched Type 2 charstrings when a contour's end point coincides with its start point (fonttools/fonttools4114, 993).
- [kernFeatureWriter] Fixed the variable-features kern writer (`variableFeatures=True`) emitting incorrect kerning values when kern group membership diverges across masters. Each pair is now resolved against each source's own groups, and classes whose membership diverges are refined into the coarsest common refinement (the same partition `varLib.merge` derives), so a family switching from varLib merging to single variable features no longer has its kerning silently mis-compiled. The same fix also applies to the legacy  `kernFeatureWriter2` (992, 996).
- [kernFeatureWriter] Fixed the variable-features kern writer hollowing kerning toward 0 across full (non-layer) UFO masters that carry no kerning at all (e.g. Roboto Flex's parametric-axis masters). Such kernless non-default sources are now skipped when building the kern `VariableScalar`s, mirroring the `varLib.merger` path's exclusion of masters that compile to no GPOS table; the default source is always kept (995, 997).

3.8.2

- [kernFeatureWriter] Fixed variable kern writer emitting phantom values when a glyph-to-class kerning exception present in only some masters overlapped a class-to-glyph exception on a shared kerning-matrix cell. Glyph-to-class exceptions are now resolved per cell rather than per pair key (988, 990). The fix covers both the default writer and the legacy `kernFeatureWriter2`, which now share the variable kerning extraction (989).

3.8.1

Fixed `Lib/ufo2ft/_version.py` file missing which caused `ufo2ft.__version__`
to be incorrectly reported as "0.0.0+unknown". This has been broken at least
since ufo2ft v3.6.7 (October 2025) when we first moved setuptools-scm config
to pyproject.toml.

3.8.0

- [instantiator] Fixed assertion error when instancing fonts with multiple sparse/virtual masters but only a single default info master (981, 983).
- [propagateAnchors] Ported the anchor propagation algorithm from glyphsLib and fontc, matching the original one from Glyphs.app (985).   
Added support for `public.openTypeCategories` in the designspace lib (now prioritized over per-UFO lib.plist).  
Allow caller (e.g. fontmake) to pass optional `preliminaryOpenTypeCategories` with a set of mark and ligature glyphs to be used by the new `propagateAnchors` when explicit `public.openTypeCategories` are not present in the source (802, 985).

Links

• PyPI: https://pypi.org/project/ufo2ft
• Changelog: https://data.safetycli.com/changelogs/ufo2ft/