Scheduled weekly dependency update for week 45 by pyup-bot · Pull Request #406 · fonttools/ufoLib2

pyup-bot · 2025-11-10T15:48:16Z

Update attrs from 25.3.0 to 25.4.0.

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

Links

PyPI: https://pypi.org/project/attrs

Update cattrs from 25.1.1 to 25.3.0.

Changelog

25.3.0

- **Potentially breaking**: [Abstract sets](https://docs.python.org/3/library/collections.abc.html#collections.abc.Set) are now structured into frozensets.
This allows hashability, better immutability and is more consistent with the [`collections.abc.Set`](https://docs.python.org/3/library/collections.abc.html#collections.abc.Set) type.
See [Migrations](https://catt.rs/en/latest/migrations.html#abstract-sets-structuring-into-frozensets) for steps to restore legacy behavior.
([686](https://github.com/python-attrs/cattrs/pull/686))
- Python 3.14 is now supported and part of the test matrix.
([653](https://github.com/python-attrs/cattrs/pull/653))
- Fix unstructuring NewTypes with the {class}`BaseConverter`.
([684](https://github.com/python-attrs/cattrs/pull/684))
- Make some Hypothesis tests more robust.
([684](https://github.com/python-attrs/cattrs/pull/684))
- {func}`cattrs.strategies.include_subclasses` now works with generic parent classes and the tagged union strategy.
([683](https://github.com/python-attrs/cattrs/pull/683))

25.2.0

- **Potentially breaking**: Sequences are now structured into tuples.
This allows hashability, better immutability and is more consistent with the [`collections.abc.Sequence`](https://docs.python.org/3/library/collections.abc.html#collections.abc.Sequence) type.
See [Migrations](https://catt.rs/en/latest/migrations.html#sequences-structuring-into-tuples) for steps to restore legacy behavior.
([663](https://github.com/python-attrs/cattrs/pull/663))
- Add a `use_alias` parameter to {class}`cattrs.Converter`.
{func}`cattrs.gen.make_dict_unstructure_fn_from_attrs`, {func}`cattrs.gen.make_dict_unstructure_fn`,
{func}`cattrs.gen.make_dict_structure_fn_from_attrs`, {func}`cattrs.gen.make_dict_structure_fn`
and {func}`cattrs.gen.typeddicts.make_dict_structure_fn` will use the value for the `use_alias` parameter from the given converter by default now.
If you&#x27;re using these functions directly, the old behavior can be restored by passing in the desired value directly.
([596](https://github.com/python-attrs/cattrs/issues/596) [#660](https://github.com/python-attrs/cattrs/pull/660))
- The [union passthrough strategy](https://catt.rs/en/stable/strategies.html#union-passthrough) now by default accepts ints for unions that contain floats but not ints,
when configured to be able to handle both ints and floats.
This more closely matches the [current typing behavior](https://typing.python.org/en/latest/spec/special-types.html#special-cases-for-float-and-complex).
([656](https://github.com/python-attrs/cattrs/issues/656) [#668](https://github.com/python-attrs/cattrs/pull/668))
- Fix unstructuring of generic classes with stringified annotations.
([661](https://github.com/python-attrs/cattrs/issues/661) [#662](https://github.com/python-attrs/cattrs/issues/662)
- For {class}`cattrs.errors.StructureHandlerNotFoundError` and {class}`cattrs.errors.ForbiddenExtraKeysError`
correctly set {attr}`BaseException.args` in `super()` and hence make them pickable.
([666](https://github.com/python-attrs/cattrs/pull/666))
- The default disambiguation hook factory is now only enabled for converters with `unstructure_strat=AS_DICT` (the default).
Since the strategy doesn&#x27;t support tuples, it is skipped for `unstructure_strat=AS_TUPLE` converters.
([673](https://github.com/python-attrs/cattrs/pull/673))
- Switch to [`uv`](https://docs.astral.sh/uv/) and [`just`](https://just.systems/man/en/) in lieu of PDM, tox and Make.
See [the Contributing section](https://catt.rs/en/v25.2.0/contributing.html#get-started) for new workflow instructions.
([671](https://github.com/python-attrs/cattrs/pull/671))

Links

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

Update fonttools from 4.59.0 to 4.60.1.

Changelog

4.60.1

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

- [ufoLib] Reverted accidental method name change in ``UFOReader.getKerningGroupConversionRenameMaps``
that broke compatibility with downstream projects like defcon (3948, 3947, robotools/defcon478).
- [ufoLib] Added test coverage for ``getKerningGroupConversionRenameMaps`` method (3950).
- [subset] Don&#x27;t try to subset BASE table; pass it through by default instead (3949).
- [subset] Remove empty BaseRecord entries in MarkBasePos lookups (3897, 3892).
- [subset] Add pruning for MarkLigPos and MarkMarkPos lookups (3946).
- [subset] Remove duplicate features when subsetting (3945).
- [Docs] Added documentation for the visitor module (3944).

4.60.0

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

- [pointPen] Allow ``reverseFlipped`` parameter of ``DecomposingPointPen`` to take a ``ReverseFlipped``
enum value to control whether/how to reverse contour direction of flipped components, in addition to
the existing True/False. This allows to set ``ReverseFlipped.ON_CURVE_FIRST`` to ensure that
the decomposed outline starts with an on-curve point before being reversed, for better consistency
with other segment-oriented contour transformations. The change is backward compatible, and the
default behavior hasn&#x27;t changed (3934).
- [filterPen] Added ``ContourFilterPointPen``, base pen for buffered contour operations, and
``OnCurveStartPointPen`` filter to ensure contours start with an on-curve point (3934).
- [cu2qu] Fixed difference in cython vs pure-python complex division by real number (3930).
- [varLib.avar] Refactored and added some new sub-modules and scripts (3926).
* ``varLib.avar.build`` module to build avar (and a missing fvar) binaries into a possibly empty TTFont,
* ``varLib.avar.unbuild`` module to print a .designspace snippet that would generate the same avar binary,
* ``varLib.avar.map`` module to take TTFont and do the mapping, in user/normalized space,
* ``varLib.avar.plan`` module moved from ``varLib.avarPlanner``.
The bare ``fonttools varLib.avar`` script is deprecated, in favour of ``fonttools varLib.avar.build`` (or ``unbuild``).
- [interpolatable] Clarify ``linear_sum_assignment`` backend options and minimal dependency
usage (3927).
- [post] Speed up ``build_psNameMapping`` (3923).
- [ufoLib] Added typing annotations to fontTools.ufoLib (3875).

4.59.2

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

- [varLib] Clear ``USE_MY_METRICS`` component flags when inconsistent across masters (3912).
- [varLib.instancer] Avoid negative advance width/height values when instatiating HVAR/VVAR,
(unlikely in well-behaved fonts) (3918).
- [subset] Fix shaping behaviour when pruning empty mark sets (3915, harfbuzz/harfbuzz5499).
- [cu2qu] Fixed ``dot()`` product of perpendicular vectors not always returning exactly 0.0
in all Python implementations (3911)
- [varLib.instancer] Implemented fully-instantiating ``avar2`` fonts (3909).
- [feaLib] Allow float values in ``VariableScalar``&#x27;s axis locations (3906, 3907).
- [cu2qu] Handle special case in ``calc_intersect`` for degenerate cubic curves where 3 to 4
control points are equal (3904).

4.59.1

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

- [featureVars] Update OS/2.usMaxContext if possible after addFeatureVariationsRaw (3894).
- [vhmtx] raise TTLibError(&#x27;not enough data...&#x27;) when hmtx/vmtx are truncated (3843, 3901).
- [feaLib] Combine duplicate features that have the same set of lookups regardless of the order in which those lookups are added to the feature (3895).
- [varLib] Deprecate ``varLib.mutator`` in favor of ``varLib.instancer``. The latter
provides equivalent full (static font) instancing in addition to partial VF instancing.
CLI users should replace ``fonttools varLib.mutator`` with ``fonttools varLib.instancer``.
API users should migrate to ``fontTools.varLib.instancer.instantiateVariableFont`` (2680).

Links

PyPI: https://pypi.org/project/fonttools
Changelog: https://data.safetycli.com/changelogs/fonttools/
Repo: http://github.com/fonttools/fonttools

Update lxml from 6.0.0 to 6.0.2.

Changelog

6.0.2

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

Bugs fixed
----------

* LP2125278: Compilation with libxml2 2.15.0 failed.
Original patch by Xi Ruoyao.

* Setting ``decompress=True`` in the parser had no effect in libxml2 2.15.

* Binary wheels on Linux and macOS use the library version libxml2 2.14.6.
See https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.14.6

* Test failures in libxml2 2.15.0 were fixed.

Other changes
-------------

* Binary wheels for Py3.9-3.11 on the ``riscv64`` architecture were added.

* Error constants were updated to match libxml2 2.15.0.

* Built using Cython 3.1.4.

6.0.1

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

Bugs fixed
----------

* LP2116333: ``lxml.sax._getNsTag()`` could fail with an exception on malformed input.

* GH467: Some test adaptations were made for libxml2 2.15.
Patch by Nick Wellnhofer.

* LP2119510, GH473: A Python compatibility test was fixed for Python 3.14+.
Patch by Lumír Balhar.

* GH471: Wheels for &quot;riscv64&quot; on recent Python versions were added.
Patch by ffgan.

* GH469: The wheel build no longer requires the ``wheel`` package unconditionally.
Patch by Miro Hrončok.

* Binary wheels use the library version libxml2 2.14.5.
See https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.14.5

* Windows binary wheels continue to use a security patched library version libxml2 2.11.9.

Links

PyPI: https://pypi.org/project/lxml
Changelog: https://data.safetycli.com/changelogs/lxml/
Homepage: https://lxml.de/

Update msgpack from 1.1.1 to 1.1.2.

Changelog

1.1.2

=====

Release Date: 2025-10-08

This release does not change source code. It updates only building wheels:

* Update Cython to v3.1.4
* Update cibuildwheel to v3.2.0
* Drop Python 3.8
* Add Python 3.14
* Add windows-arm

Links

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

Update orjson from 3.11.0 to 3.11.4.

Changelog

3.11.4

Changed

- ABI compatibility with CPython 3.15 alpha 1.
- Publish PyPI wheels for 3.14 and manylinux i686, manylinux arm7,
manylinux ppc64le, manylinux s390x.
- Build now requires a C compiler.

3.11.3

Fixed

- Fix PyPI project metadata when using maturin 1.9.2 or later.

3.11.2

Fixed

- Fix build using Rust 1.89 on amd64.

Changed

- Build now depends on Rust 1.85 or later instead of 1.82.

3.11.1

Changed

- Publish PyPI wheels for CPython 3.14.

Fixed

- Fix `str` on big-endian architectures. This was introduced in 3.11.0.

Links

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

Update typing-extensions from 4.14.1 to 4.15.0.

Changelog

4.15.0

No user-facing changes since 4.15.0rc1.

4.15.0rc1

- Add the `typing_extensions.disjoint_base` decorator, as specified
in PEP 800. Patch by Jelle Zijlstra.
- Add `typing_extensions.type_repr`, a backport of
[`annotationlib.type_repr`](https://docs.python.org/3.14/library/annotationlib.html#annotationlib.type_repr),
introduced in Python 3.14 (CPython PR [124551](https://github.com/python/cpython/pull/124551),
originally by Jelle Zijlstra). Patch by Semyon Moroz.
- Fix behavior of type params in `typing_extensions.evaluate_forward_ref`. Backport of
CPython PR [137227](https://github.com/python/cpython/pull/137227) by Jelle Zijlstra.

Links

PyPI: https://pypi.org/project/typing-extensions
Changelog: https://data.safetycli.com/changelogs/typing-extensions/

Update black from 25.1.0 to 25.11.0.

Changelog

25.11.0

Highlights

- Enable base 3.14 support (4804)
- Add support for the new Python 3.14 t-string syntax introduced by PEP 750 (4805)

Stable style

- Fix bug where comments between ` fmt: off` and ` fmt: on` were reformatted (4811)
- Comments containing fmt directives now preserve their exact formatting instead of
being normalized (4811)

Preview style

- Move `multiline_string_handling` from `--unstable` to `--preview` (4760)
- Fix bug where module docstrings would be treated as normal strings if preceded by
comments (4764)
- Fix bug where python 3.12 generics syntax split line happens weirdly (4777)
- Standardize type comments to form ` type: &lt;value&gt;` (4645)
- Fix `fix_fmt_skip_in_one_liners` preview feature to respect ` fmt: skip` for compound
statements with semicolon-separated bodies (4800)

Configuration

- Add `no_cache` option to control caching behavior. (4803)

Packaging

- Releases now include arm64 Linux binaries (4773)

Output

- Write unchanged content to stdout when excluding formatting from stdin using pipes
(4610)

_Blackd_

- Implemented BlackDClient. This simple python client allows to easily send formatting
requests to blackd (4774)

Integrations

- Enable 3.14 base CI (4804)
- Enhance GitHub Action `psf/black` to support the `required-version` major-version-only
&quot;stability&quot; format when using pyproject.toml (4770)
- Improve error message for vim plugin users. It now handles independently vim version
- Vim: Warn on unsupported Vim and Python versions independently (4772)
- Vim: Print the import paths when importing black fails (4675)
- Vim: Fix handling of virtualenvs that have a different Python version (4675)

25.9.0

Highlights

- Remove support for pre-python 3.7 `await/async` as soft keywords/variable names
(4676)

Stable style

- Fix crash while formatting a long `del` statement containing tuples (4628)
- Fix crash while formatting expressions using the walrus operator in complex `with`
statements (4630)
- Handle ` fmt: skip` followed by a comment at the end of file (4635)
- Fix crash when a tuple appears in the `as` clause of a `with` statement (4634)
- Fix crash when tuple is used as a context manager inside a `with` statement (4646)
- Fix crash when formatting a `\` followed by a `\r` followed by a comment (4663)
- Fix crash on a `\\r\n` (4673)
- Fix crash on `await ...` (where `...` is a literal `Ellipsis`) (4676)
- Fix crash on parenthesized expression inside a type parameter bound (4684)
- Fix crash when using line ranges excluding indented single line decorated items
(4670)

Preview style

- Fix a bug where one-liner functions/conditionals marked with ` fmt: skip` would still
be formatted (4552)
- Improve `multiline_string_handling` with ternaries and dictionaries (4657)
- Fix a bug where `string_processing` would not split f-strings directly after
expressions (4680)
- Wrap the `in` clause of comprehensions across lines if necessary (4699)
- Remove parentheses around multiple exception types in `except` and `except*` without
`as`. (4720)
- Add `\r` style newlines to the potential newlines to normalize file newlines both from
and to (4710)

Parser

- Rewrite tokenizer to improve performance and compliance (4536)
- Fix bug where certain unusual expressions (e.g., lambdas) were not accepted in type
parameter bounds and defaults. (4602)

Performance

- Avoid using an extra process when running with only one worker (4734)

Integrations

- Fix the version check in the vim file to reject Python 3.8 (4567)
- Enhance GitHub Action `psf/black` to read Black version from an additional section in
pyproject.toml: `[project.dependency-groups]` (4606)
- Build gallery docker image with python3-slim and reduce image size (4686)

Documentation

- Add FAQ entry for windows emoji not displaying (4714)

Links

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

Update click from 8.1.8 to 8.3.0.

Changelog

8.3.0

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

Released 2025-09-15

-   **Improved flag option handling**: Reworked the relationship between ``flag_value``
 and ``default`` parameters for better consistency:

 * The ``default`` parameter value is now preserved as-is and passed directly
   to CLI functions (no more unexpected transformations)
 * Exception: flag options with ``default=True`` maintain backward compatibility
   by defaulting to their ``flag_value``
 * The ``default`` parameter can now be any type (``bool``, ``None``, etc.)
 * Fixes inconsistencies reported in: :issue:`1992` :issue:`2514` :issue:`2610`
   :issue:`3024` :pr:`3030`
-   Allow ``default`` to be set on ``Argument`` for ``nargs = -1``. :issue:`2164`
 :pr:`3030`
-   Show correct auto complete value for ``nargs`` option in combination with flag
 option :issue:`2813`
-   Show correct auto complete value for nargs option in combination with flag option :issue:`2813`
-   Fix handling of quoted and escaped parameters in Fish autocompletion. :issue:`2995` :pr:`3013`
-   Lazily import ``shutil``. :pr:`3023`
-   Properly forward exception information to resources registered with
 ``click.core.Context.with_resource()``. :issue:`2447` :pr:`3058`
-   Fix regression related to EOF handling in CliRunner. :issue:`2939`:pr:`2940`

8.2.2

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

Released 2025-07-31

-   Fix reconciliation of ``default``, ``flag_value`` and ``type`` parameters for
 flag options, as well as parsing and normalization of environment variables.
 :issue:`2952` :pr:`2956`
-   Fix typing issue in ``BadParameter`` and ``MissingParameter`` exceptions for the
 parameter ``param_hint`` that did not allow for a sequence of string where the
 underlying function ``_join_param_hints`` allows for it. :issue:`2777` :pr:`2990`
-   Use the value of ``Enum`` choices to render their default value in help
 screen. Refs :issue:`2911` :pr:`3004`
-   Fix completion for the Z shell (``zsh``) for completion items containing
 colons. :issue:`2703` :pr:`2846`
-   Don&#x27;t include envvar in error hint when not configured. :issue:`2971` :pr:`2972`
-   Fix a rare race in ``click.testing.StreamMixer``&#x27;s finalization that manifested
 as a ``ValueError`` on close in a multi-threaded test session.
 :issue:`2993` :pr:`2991`

8.2.1

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

Released 2025-05-20

-   Fix flag value handling for flag options with a provided type. :issue:`2894`
 :issue:`2897` :pr:`2930`
-   Fix shell completion for nested groups. :issue:`2906` :pr:`2907`
-   Flush ``sys.stderr`` at the end of ``CliRunner.invoke``. :issue:`2682`
-   Fix EOF handling for stdin input in CliRunner. :issue:`2787`

8.2.0

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

Released 2025-05-10

-   Drop support for Python 3.7, 3.8, and 3.9. :pr:`2588` :pr:`2893`
-   Use modern packaging metadata with ``pyproject.toml`` instead of ``setup.cfg``.
 :pr:`2438`
-   Use ``flit_core`` instead of ``setuptools`` as build backend. :pr:`2543`
-   Deprecate the ``__version__`` attribute. Use feature detection, or
 ``importlib.metadata.version(&quot;click&quot;)``, instead. :issue:`2598`
-   ``BaseCommand`` is deprecated. ``Command`` is the base class for all
 commands. :issue:`2589`
-   ``MultiCommand`` is deprecated. ``Group`` is the base class for all group
 commands. :issue:`2590`
-   The current parser and related classes and methods, are deprecated.
 :issue:`2205`

 -   ``OptionParser`` and the ``parser`` module, which is a modified copy of
     ``optparse`` in the standard library.
 -   ``Context.protected_args`` is unneeded. ``Context.args`` contains any
     remaining arguments while parsing.
 -   ``Parameter.add_to_parser`` (on both ``Argument`` and ``Option``) is
     unneeded. Parsing works directly without building a separate parser.
 -   ``split_arg_string`` is moved from ``parser`` to ``shell_completion``.

-   Enable deferred evaluation of annotations with
 ``from __future__ import annotations``. :pr:`2270`
-   When generating a command&#x27;s name from a decorated function&#x27;s name, the
 suffixes ``_command``, ``_cmd``, ``_group``, and ``_grp`` are removed.
 :issue:`2322`
-   Show the ``types.ParamType.name`` for ``types.Choice`` options within
 ``--help`` message if ``show_choices=False`` is specified.
 :issue:`2356`
-   Do not display default values in prompts when ``Option.show_default`` is
 ``False``. :pr:`2509`
-   Add ``get_help_extra`` method on ``Option`` to fetch the generated extra
 items used in ``get_help_record`` to render help text. :issue:`2516`
 :pr:`2517`
-   Keep stdout and stderr streams independent in ``CliRunner``. Always
 collect stderr output and never raise an exception. Add a new
 output stream to simulate what the user sees in its terminal. Removes
 the ``mix_stderr`` parameter in ``CliRunner``. :issue:`2522` :pr:`2523`
-   ``Option.show_envvar`` now also shows environment variable in error messages.
 :issue:`2695` :pr:`2696`
-   ``Context.close`` will be called on exit. This results in all
 ``Context.call_on_close`` callbacks and context managers added via
 ``Context.with_resource`` to be closed on exit as well. :pr:`2680`
-   Add ``ProgressBar(hidden: bool)`` to allow hiding the progressbar. :issue:`2609`
-   A ``UserWarning`` will be shown when multiple parameters attempt to use the
 same name. :issue:`2396`
-   When using ``Option.envvar`` with ``Option.flag_value``, the ``flag_value``
 will always be used instead of the value of the environment variable.
 :issue:`2746` :pr:`2788`
-   Add ``Choice.get_invalid_choice_message`` method for customizing the
 invalid choice message. :issue:`2621` :pr:`2622`
-   If help is shown because ``no_args_is_help`` is enabled (defaults to ``True``
 for groups, ``False`` for commands), the exit code is 2 instead of 0.
 :issue:`1489` :pr:`1489`
-   Contexts created during shell completion are closed properly, fixing
 a ``ResourceWarning`` when using ``click.File``. :issue:`2644` :pr:`2800`
 :pr:`2767`
-   ``click.edit(filename)`` now supports passing an iterable of filenames in
 case the editor supports editing multiple files at once. Its return type
 is now also typed: ``AnyStr`` if ``text`` is passed, otherwise ``None``.
 :issue:`2067` :pr:`2068`
-   Specialized typing of ``progressbar(length=...)`` as ``ProgressBar[int]``.
 :pr:`2630`
-   Improve ``echo_via_pager`` behaviour in face of errors.
 :issue:`2674`

 -   Terminate the pager in case a generator passed to ``echo_via_pager``
     raises an exception.
 -   Ensure to always close the pipe to the pager process and wait for it
     to terminate.
 -   ``echo_via_pager`` will not ignore ``KeyboardInterrupt`` anymore. This
     allows the user to search for future output of the generator when
     using less and then aborting the program using ctrl-c.

-   ``deprecated: bool | str`` can now be used on options and arguments. This
 previously was only available for ``Command``. The message can now also be
 customised by using a ``str`` instead of a ``bool``. :issue:`2263` :pr:`2271`

 -   ``Command.deprecated`` formatting in ``--help`` changed from
     ``(Deprecated) help`` to ``help (DEPRECATED)``.
 -   Parameters cannot be required nor prompted or an error is raised.
 -   A warning will be printed when something deprecated is used.

-   Add a ``catch_exceptions`` parameter to ``CliRunner``. If
 ``catch_exceptions`` is not passed to ``CliRunner.invoke``, the value
 from ``CliRunner`` is used. :issue:`2817` :pr:`2818`
-   ``Option.flag_value`` will no longer have a default value set based on
 ``Option.default`` if ``Option.is_flag`` is ``False``. This results in
 ``Option.default`` not needing to implement `__bool__`. :pr:`2829`
-   Incorrect ``click.edit`` typing has been corrected. :pr:`2804`
-   ``Choice`` is now generic and supports any iterable value.
 This allows you to use enums and other non-``str`` values. :pr:`2796`
 :issue:`605`
-   Fix setup of help option&#x27;s defaults when using a custom class on its
 decorator. Removes ``HelpOption``. :issue:`2832` :pr:`2840`

Links

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

Update coverage from 7.9.2 to 7.11.3.

Changelog

7.11.3

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

- Fix: the 7.11.1 changes meant that conflicts between a requested measurement
core and other settings would raise an error. This was a breaking change from
previous behavior, as reported in `issue 2076`_ and `issue 2078`_.

The previous behavior has been restored: when the requested core conflicts
with other settings, another core is used instead, and a warning is issued.

- For contributors: the repo has moved from Ned&#x27;s `nedbat GitHub account`_ to
the `coveragepy GitHub organization`_. The default branch has changed from
master to main.

.. _issue 2076: https://github.com/coveragepy/coveragepy/issues/2076
.. _issue 2078: https://github.com/coveragepy/coveragepy/issues/2078
.. _nedbat GitHub account: https://github.com/nedbat
.. _coveragepy GitHub organization: https://github.com/coveragepy


.. _changes_7-11-2:

7.11.2

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

- Fix: using the &quot;sysmon&quot; measurement core in 7.11.1, if Python code was
claimed to come from a non-Python file, a ``NotPython`` exception could be
raised. This could happen for example with Jinja templates compiled to
Python, as reported in `issue 2077`_. This is now fixed.

- Doc: corrected the first entry in the 7.11.1 changelog.

.. _issue 2077: https://github.com/coveragepy/coveragepy/issues/2077


.. _changes_7-11-1:

7.11.1

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

- Fix: some chanages to details of how the measurement core is chosen, and how
conflicting settings are handled. The &quot;sysmon&quot; core cannot be used with some
conurrency settings, with dynamic context, and in Python 3.12/3.13, with
branch measurement.

- If the core is not specified and defaults to &quot;sysmon&quot; (Python 3.14+), but
 other settings conflict with sysmon, then the &quot;ctrace&quot; core will be used
 instead with no warning. For concurrency conflicts, this used to produce an
 error, as described in `issue 2064`_.

- If the &quot;sysmon&quot; core is explicitly requested in your configuration, but
 other settings conflict, an error is now raised. This used to produce a
 warning.

- Fix: some multi-line case clauses or for loops (and probably other
constructs) could cause incorrect claims of missing branches with the
sys.monitoring core, as described in `issue 2070`_. This is now fixed.

- Fix: when running in pytest under coverage, a ``breakpoint()`` would stop in
the wrong frame, one level down from where it should, as described in `issue
1420`_. This was due to a coverage change in v6.4.1 that seemed to give a
slight performance improvement, but I couldn&#x27;t reproduce the performance
gain, so it&#x27;s been reverted, fixing the debugger problem.

- A new debug option ``--debug=core`` shows which core is in use and why.

- Split ``sqlite`` debugging information out of the ``sys`` :ref:`coverage
debug &lt;cmd_debug&gt;` and :ref:`cmd_run_debug` options since it&#x27;s bulky and not
very useful.

- Updated the :ref:`howitworks` page to better describe the three different
measurement cores.

.. _issue 1420: https://github.com/coveragepy/coveragepy/issues/1420
.. _issue 2064: https://github.com/coveragepy/coveragepy/issues/2064
.. _issue 2070: https://github.com/coveragepy/coveragepy/issues/2070


.. _changes_7-11-0:

7.11.0

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

- Dropped support for Python 3.9, declared support for Python 3.15 alpha.


.. _changes_7-10-7:

7.10.7

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

- Performance: with branch coverage in large files, generating HTML, JSON, or
LCOV reports could take far too long due to some quadratic behavior when
creating the function and class index pages.  This is now fixed, closing
`issue 2048`_.  Thanks to Daniel Diniz for help diagnosing the problem.

- Most warnings and a few errors now have links to a page in the docs
explaining the specific message.  Closes `issue 1921`_.

.. _issue 1921: https://github.com/coveragepy/coveragepy/issues/1921
.. _issue 2048: https://github.com/coveragepy/coveragepy/issues/2048


.. _changes_7-10-6:

7.10.6

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

- Fix: ``source`` directories were not properly communicated to subprocesses
that ran in different directories, as reported in `issue 1499`_.  This is now
fixed.

- Performance: `Alex Gaynor continues fine-tuning &lt;pull 2038_&gt;`_ the speed of
combination, especially with many contexts.

.. _issue 1499: https://github.com/coveragepy/coveragepy/issues/1499
.. _pull 2038: https://github.com/coveragepy/coveragepy/pull/2038


.. _changes_7-10-5:

7.10.5

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

- Big speed improvements for ``coverage combine``: it&#x27;s now about twice as
fast! Huge thanks to Alex Gaynor for pull requests `2032 &lt;pull 2032_&gt;`_,
`2033 &lt;pull 2033_&gt;`_, and `2034 &lt;pull 2034_&gt;`_.

.. _pull 2032: https://github.com/coveragepy/coveragepy/pull/2032
.. _pull 2033: https://github.com/coveragepy/coveragepy/pull/2033
.. _pull 2034: https://github.com/coveragepy/coveragepy/pull/2034


.. _changes_7-10-4:

7.10.4

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

- Added ``patch = fork`` for times when the built-in forking support is
insufficient.

- Fix: ``patch = execv`` also inherits the entire coverage configuration now.


.. _changes_7-10-3:

7.10.3

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

- Fixes for ``patch = subprocess``:

- If subprocesses spawned yet more subprocesses simultaneously, some coverage
 could be missed.  This is now fixed, closing `issue 2024`_.

- If subprocesses were created in other directories, their data files were
 stranded there and not combined into the totals, as described in `issue
 2025`_.  This is now fixed.

- On Windows (or maybe only some Windows?) the patch would fail with a
 ``ModuleNotFound`` error trying to import coverage.  This is now fixed,
 closing `issue 2022`_.

- Originally only options set in the coverage configuration file would apply
 to subprocesses.  Options set on the ``coverage run`` command line (such as
 ``--branch``) wouldn&#x27;t be communicated to the subprocesses.  This could
 lead to combining failures, as described in `issue 2021`_. Now the entire
 configuration is used in subprocesses, regardless of its origin.

- Added ``debug=patch`` to help diagnose problems.

- Fix: really close all SQLite databases, even in-memory ones. Closes `issue
2017`_.

.. _issue 2017: https://github.com/coveragepy/coveragepy/issues/2017
.. _issue 2021: https://github.com/coveragepy/coveragepy/issues/2021
.. _issue 2022: https://github.com/coveragepy/coveragepy/issues/2022
.. _issue 2024: https://github.com/coveragepy/coveragepy/issues/2024
.. _issue 2025: https://github.com/coveragepy/coveragepy/issues/2025


.. _changes_7-10-2:

7.10.2

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

- Fix: some code with NOP bytecodes could report missing branches that are
actually executed. This is now fixed, closing `issue 1999`_. Python 3.9
still shows the problem.

.. _issue 1999: https://github.com/coveragepy/coveragepy/issues/1999


.. _changes_7-10-1:

7.10.1

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

- Fix: the exclusion for ``if TYPE_CHECKING:`` was wrong: it marked the branch
as partial, but it should have been a line exclusion so the entire clause
would be excluded. Improves `issue 831`_.

- Fix: changed where .pth files are written for ``patch = subprocess``, closing
`issue 2006`_.

.. _issue 2006: https://github.com/coveragepy/coveragepy/issues/2006


.. _changes_7-10-0:

7.10.0

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

- A new configuration option: &quot;:ref:`config_run_patch`&quot; specifies named patches
to work around some limitations in coverage measurement.  These patches are
available:

- ``patch = _exit`` lets coverage save its data even when :func:`os._exit()
 &lt;python:os._exit&gt;` is used to abruptly end the process.  This closes
 long-standing `issue 310`_ as well as its duplicates: `issue 312`_, `issue
 1673`_, `issue 1845`_, and `issue 1941`_.

- ``patch = subprocess`` measures coverage in Python subprocesses created
 with :mod:`subprocess`, :func:`os.system`, or one of the :func:`execv
 &lt;python:os.execl&gt;` or :func:`spawnv &lt;python:os.spawnl&gt;` family of
 functions. Closes old `issue 367`_, its duplicate `issue 378`_ and old
 `issue 689`_.

- ``patch = execv`` adjusts the :func:`execv &lt;python:os.execl&gt;` family of
 functions to save coverage data before ending the current program and
 starting the next. Not available on Windows. Closes `issue 43`_ after 15
 years!

- The HTML report now dimly colors subsequent lines in multi-line statements.
They used to have no color.  This gives a better indication of the amount of
code missing in the report.  Closes `issue 1308`_.

- Two new exclusion patterns are part of the defaults: ``...`` is automatically
excluded as a line and ``if TYPE_CHECKING:`` is excluded as a branch.  Closes
`issue 831`_.

- A new command-line option: ``--save-signal=USR1`` specifies a signal that
coverage.py will listen for.  When the signal is sent, the coverage data will
be saved.  This makes it possible to save data from within long-running
processes.  Thanks, `Arkady Gilinsky &lt;pull 1998_&gt;`_.

- A new configuration option: &quot;:ref:`config_report_partial_also`&quot; is a list of
regexes to add as pragmas for partial branches.  This parallels the
&quot;:ref:`config_report_exclude_also`&quot; setting for adding line exclusion
patterns.

- A few file path configuration settings didn&#x27;t allow for tilde expansion:
:ref:`config_json_output`, :ref:`config_lcov_output` and
:ref:`config_run_debug_file`.  This is now fixed.

- Wheels are included for 3.14 now that 3.14 rc1 is available.

- We no longer ship a PyPy-specific wheel. PyPy will install the pure-Python
wheel.  Closes `issue 2001`_.

- In the very unusual situation of not having a current frame, coverage no
longer crashes when using the sysmon core, fixing `issue 2005`_.

.. _issue 43: https://github.com/coveragepy/coveragepy/issues/43
.. _issue 310: https://github.com/coveragepy/coveragepy/issues/310
.. _issue 312: https://github.com/coveragepy/coveragepy/issues/312
.. _issue 367: https://github.com/coveragepy/coveragepy/issues/367
.. _issue 378: https://github.com/coveragepy/coveragepy/issues/378
.. _issue 689: https://github.com/coveragepy/coveragepy/issues/689
.. _issue 831: https://github.com/coveragepy/coveragepy/issues/831
.. _issue 1308: https://github.com/coveragepy/coveragepy/issues/1308
.. _issue 1673: https://github.com/coveragepy/coveragepy/issues/1673
.. _issue 1845: https://github.com/coveragepy/coveragepy/issues/1845
.. _issue 1941: https://github.com/coveragepy/coveragepy/issues/1941
.. _pull 1998: https://github.com/coveragepy/coveragepy/pull/1998
.. _issue 2001: https://github.com/coveragepy/coveragepy/issues/2001
.. _issue 2005: https://github.com/coveragepy/coveragepy/issues/2005

.. _changes_7-9-2:

Links

PyPI: https://pypi.org/project/coverage
Changelog: https://data.safetycli.com/changelogs/coverage/
Repo: https://github.com/coveragepy/coveragepy

Update iniconfig from 2.1.0 to 2.3.0.

Changelog

2.2.0

=====

* drop Python 3.8 and 3.9 support (now requires Python &gt;= 3.10)
* add Python 3.14 classifier
* migrate from hatchling to setuptools 77 with setuptools_scm
* adopt PEP 639 license specifiers and PEP 740 build attestations
* migrate from black + pyupgrade to ruff
* migrate CI to uv and unified test workflow
* automate GitHub releases and PyPI publishing via Trusted Publishing
* include tests in sdist
* modernize code for Python 3.10+ (remove __future__ annotations, TYPE_CHECKING guards)
* rename _ParsedLine to ParsedLine

Links

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

Update isort from 6.0.1 to 7.0.0.

Changelog

6.1.0

- Add python 3.14 classifier and badge (2409) staticdev
- Drop use of non-standard pkg_resources API (2405) dvarrazzo

Links

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

Update mypy from 1.17.0 to 1.18.2.

Changelog

1.18.2

- Fix crash on recursive alias (Ivan Levkivskyi, PR [19845](https://github.com/python/mypy/pull/19845))
- Add additional guidance for stubtest errors when runtime is `object.__init__` (Stephen Morton, PR [19733](https://github.com/python/mypy/pull/19733))
- Fix handling of None values in f-string expressions in mypyc (BobTheBuidler, PR [19846](https://github.com/python/mypy/pull/19846))

Acknowledgements

Thanks to all mypy contributors who contributed to this release:

- Ali Hamdan
- Anthony Sottile
- BobTheBuidler
- Brian Schubert
- Chainfire
- Charlie Denton
- Christoph Tyralla
- CoolCat467
- Daniel Hnyk
- Emily
- Emma Smith
- Ethan Sarp
- Ivan Levkivskyi
- Jahongir Qurbonov
- Jelle Zijlstra
- Joren Hammudoglu
- Jukka Lehtosalo
- Marc Mueller
- Omer Hadari
- Piotr Sawicki
- PrinceNaroliya
- Randolf Scholz
- Robsdedude
- Saul Shanabrook
- Shantanu
- Stanislav Terliakov
- Stephen Morton
- wyattscarpenter

I’d also like to thank my employer, Dropbox, for supporting mypy development.

1.18.1

compared to 1.17 when type checking mypy itself. In extreme cases, the improvement
can be 10x or higher. The list below is an overview of the various mypy optimizations.
Many mypyc improvements (discussed in a separate section below) also improve performance.

Type caching optimizations have a small risk of causing regressions. When
reporting issues with unexpected inferred types, please also check if
`--disable-expression-cache` will work around the issue, as it turns off some of
these optimizations.

- Improve self check performance by 1.8% (Jukka Lehtosalo, PR [19768](https://github.com/python/mypy/pull/19768), [19769](https://github.com/python/mypy/pull/19769), [19770](https://github.com/python/mypy/pull/19770))
- Optimize fixed-format deserialization (Ivan Levkivskyi, PR [19765](https://github.com/python/mypy/pull/19765))
- Use macros to optimize fixed-format deserialization (Ivan Levkivskyi, PR [19757](https://github.com/python/mypy/pull/19757))
- Two additional micro‑optimizations (Ivan Levkivskyi, PR [19627](https://github.com/python/mypy/pull/19627))
- Another set of micro‑optimizations (Ivan Levkivskyi, PR [19633](https://github.com/python/mypy/pull/19633))
- Cache common types (Ivan Levkivskyi, PR [19621](https://github.com/python/mypy/pull/19621))
- Skip more method bodies in third‑party libraries for speed (Ivan Levkivskyi, PR [19586](https://github.com/python/mypy/pull/19586))
- Simplify the representation of callable types (Ivan Levkivskyi, PR [19580](https://github.com/python/mypy/pull/19580))
- Add cache for types of some expressions (Ivan Levkivskyi, PR [19505](https://github.com/python/mypy/pull/19505))
- Use cache for dictionary expressions (Ivan Levkivskyi, PR [19536](https://github.com/python/mypy/pull/19536))
- Use cache for binary operations (Ivan Levkivskyi, PR [19523](https://github.com/python/mypy/pull/19523))
- Cache types of type objects (Ivan Levkivskyi, PR [19514](https://github.com/python/mypy/pull/19514))
- Avoid duplicate work when checking boolean operations (Ivan Levkivskyi, PR [19515](https://github.com/python/mypy/pull/19515))
- Optimize generic inference passes (Ivan Levkivskyi, PR [19501](https://github.com/python/mypy/pull/19501))
- Speed up the default plugin (Jukka Lehtosalo, PRs [19385](https://github.com/python/mypy/pull/19385) and [19462](https://github.com/python/mypy/pull/19462))
- Remove nested imports from the default plugin (Ivan Levkivskyi, PR [19388](https://github.com/python/mypy/pull/19388))
- Micro‑optimize type expansion (Jukka Lehtosalo, PR [19461](https://github.com/python/mypy/pull/19461))
- Micro‑optimize type indirection (Jukka Lehtosalo, PR [19460](https://github.com/python/mypy/pull/19460))
- Micro‑optimize the plugin framework (Jukka Lehtosalo, PR [19464](https://github.com/python/mypy/pull/19464))
- Avoid temporary set creation in subtype checking (Jukka Lehtosalo, PR [19463](https://github.com/python/mypy/pull/19463))
- Subtype checking micro‑optimization (Jukka Lehtosalo, PR [19384](https://github.com/python/mypy/pull/19384))
- Return early where possible in subtype check (Stanislav Terliakov, PR [19400](https://github.com/python/mypy/pull/19400))
- Deduplicate some types before joining (Stanislav Terliakov, PR [19409](https://github.com/python/mypy/pull/19409))
- Speed up type checking by caching argument inference context (Jukka Lehtosalo, PR [19323](https://github.com/python/mypy/pull/19323))
- Optimize binding method self argument type and deprecation checks (Ivan Levkivskyi, PR [19556](https://github.com/python/mypy/pull/19556))
- Keep trivial instance types/aliases during expansion (Ivan Levkivskyi, PR [19543](https://github.com/python/mypy/pull/19543))

Fixed‑Format Cache (Experimental)

Mypy now supports a new cache format used for faster incremental builds. It makes
incremental builds up to twice as fast. The feature is experimental and
currently only supported when using a compiled version of mypy. Use `--fixed-format-cache`
to enable the new format, or `fixed_format_cache = True` in a configuration file.

We plan to enable this by default in a future mypy release, and we&#x27;ll eventually
deprecate and remove support for the original JSON-based format.

Unlike the JSON-based cache format, the new binary format is currently
not easy to parse and inspect by mypy users. We are planning to provide a tool to
convert fixed-format cache files to JSON, but details of the output JSON may be
different from the current JSON format. If you rely on being able to inspect
mypy cache files, we recommend creating a GitHub issue and explaining your use
case, so that we can more likely provide support for it. (Using
`MypyFile.read(binary_data)` to inspect cache data may be sufficient to support
some use cases.)

This feature was contributed by Ivan Levkivskyi (PR [19668](https://github.com/python/mypy/pull/19668), [19735](https://github.com/python/mypy/pull/19735), [19750](https://github.com/python/mypy/pull/19750), [19681](https://github.com/python/mypy/pull/19681), [19752](https://github.com/python/mypy/pull/19752), [19815](https://github.com/python/mypy/pull/19815)).

Flexible Variable Definitions: Update

1.17.1

* Retain `None` as constraints bottom if no bottoms were provided (Stanislav Terliakov, PR [19485](https://github.com/python/mypy/pull/19485))
* Fix &quot;ignored exception in `hasattr`&quot; in dmypy (Stanislav Terliakov, PR [19428](https://github.com/python/mypy/pull/19428))
* Prevent a crash when InitVar is redefined with a method in a subclass (Stanislav Terliakov, PR [19453](https://github.com/python/mypy/pull/19453))

Acknowledgements

Thanks to all mypy contributors who contributed to this release:

* Alexey Makridenko
* Brian Schubert
* Chad Dombrova
* Chainfire
* Charlie Denton
* Charulata
* Christoph Tyralla
* CoolCat467
* Donal Burns
* Guy Wilson
* Ivan Levkivskyi
* johnthagen
* Jukka Lehtosalo
* Łukasz Kwieciński
* Marc Mueller
* Michael J. Sullivan
* Mikhail Golubev
* Sebastian Rittau
* Shantanu
* Stanislav Terliakov
* wyattscarpenter

I’d also like to thank my employer, Dropbox, for supporting mypy development.

Links

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

Update platformdirs from 4.3.8 to 4.5.0.

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

Links

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

Update pytest from 8.4.1 to 9.0.0.

Changelog

9.0.0

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

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


- `1367 &lt;https://github.com/pytest-dev/pytest/issues/1367&gt;`_: **Support for subtests** has been added.

:ref:`subtests &lt;subtests&gt;` are an alternative to parametrization, useful in situations where the parametrization values are not all known at collection time.

Example:

.. code-block:: python

   def contains_docstring(p: Path) -&gt; bool:
       &quot;&quot;&quot;Return True if the given Python file contains a top-level docstring.&quot;&quot;&quot;
       ...


   def test_py_files_contain_docstring(subtests: pytest.Subtests) -&gt; None:
       for path in Path.cwd().glob(&quot;*.py&quot;):
           with subtests.test(path=str(path)):
               assert contains_docstring(path)


Each assert failure or error is caught by the context manager and reported individually, giving a clear picture of all files that are missing a docstring.

In addition, :meth:`unittest.TestCase.subTest` is now also supported.

This feature was originally implemented as a separate plugin in `pytest-subtests &lt;https://github.com/pytest-dev/pytest-subtests&gt;`__, but since then has been merged into the core.

.. note::

   This feature is experimental and will likely evolve in future releases. By that we mean that we might change how subtests are reported on failure, but the functionality and how to use it are stable.


- `13743 &lt;https://github.com/pytest-dev/pytest/issues/13743&gt;`_: Added support for **native TOML configuration files**.

While pytest, since version 6, supports configuration in ``pyproject.toml`` files under ``[tool.pytest.ini_options]``,
it does so in an &quot;INI compatibility mode&quot;, where all configuration values are treated as strings or list of strings.
Now, pytest supports the native TOML data model.

In ``pyproject.toml``, the native TOML configuration is under the ``[tool.pytest]`` table.

.. code-block:: toml

    pyproject.toml
   [tool.pytest]
   minversion = &quot;9.0&quot;
   addopts = [&quot;-ra&quot;, &quot;-q&quot;]
   testpaths = [
       &quot;tests&quot;,
       &quot;integration&quot;,
   ]

The ``[tool.pytest.ini_options]`` table remains supported, but both tables cannot be used at the same time.

If you prefer to use a separate configuration file, or don&#x27;t use ``pyproject.toml``, you can use ``pytest.toml`` or ``.pytest.toml``:

.. code-block:: toml

    pytest.toml or .pytest.toml
   [pytest]
   minversion = &quot;9.0&quot;
   addopts = [&quot;-ra&quot;, &quot;-q&quot;]
   testpaths = [
       &quot;tests&quot;,
       &quot;integration&quot;,
   ]

The documentation now (sometimes) shows configuration snippets in both TOML and INI formats, in a tabbed interface.

See :ref:`config file formats` for full details.


- `13823 &lt;https://github.com/pytest-dev/pytest/issues/13823&gt;`_: Added a **&quot;strict mode&quot;** enabled by the :confval:`strict` configuration option.

When set to ``true``, the :confval:`strict` option currently enables

* :confval:`strict_config`
* :confval:`strict_markers`
* :confval:`strict_parametrization_ids`
* :confval:`strict_xfail`

The individual strictness options can be explicitly set to override the global :confval:`strict` setting.

The previously-deprecated ``--strict`` command-line flag now enables strict mode.

If pytest adds new strictness options in the future, they will also be enabled in strict mode.
Therefore, you should only enable strict mode if you use a pinned/locked version of pytest,
or if you want to proactively adopt new strictness options as they are added.

See :ref:`strict mode` for more details.


- `13737 &lt;https://github.com/pytest-dev/pytest/issues/13737&gt;`_: Added the :confval:`strict_parametrization_ids` configuration option.

When set, pytest emits an error if it detects non-unique parameter set IDs,
rather than automatically making the IDs unique by adding `0`, `1`, ... to them.
This can be particularly useful for catching unintended duplicates.


- `13072 &lt;https://github.com/pytest-dev/pytest/issues/13072&gt;`_: Added support for displaying test session **progress in the terminal tab** using the `OSC 9;4; &lt;https://conemu.github.io/en/AnsiEscapeCodes.html#ConEmu_specific_OSC&gt;`_ ANSI sequence.
When pytest runs in a supported terminal emulator like ConEmu, Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty,
you&#x27;ll see the progress in the terminal tab or window,
allowing you to monitor pytest&#x27;s progress at a glance.

This feature is automatically enabled when running in a TTY. It is implemented as an internal plugin. If needed, it can be disabled as follows:
- On a user level, using ``-p no:terminalprogress`` on the command line or via an environment variable ``PYTEST_ADDOPTS=&#x27;-p no:terminalprogress&#x27;``.
- On a project configuration level, using ``addopts = &quot;-p no:terminalprogress&quot;``.


- `478 &lt;https://github.com/pytest-dev/pytest/issues/478&gt;`_: Support PEP420 (implicit namespace packages) as `--pyargs` target when :confval:`consider_namespace_packages` is `true` in the config.

Previously, this option only impacted package imports, now it also impacts tests discovery.


- `13678 &lt;https://github.com/pytest-dev/pytest/issues/13678&gt;`_: Added a new :confval:`faulthandler_exit_on_timeout` configuration option set to &quot;false&quot; by default to let `faulthandler` interrupt the `pytest` process after a timeout in case of deadlock.

Previously, a `faulthandler` timeout would only dump the traceback of all threads to stderr, but would not interrupt the `pytest` process.

-- by :user:`ogrisel`.


- `13829 &lt;https://github.com/pytest-dev/pytest/issues/13829&gt;`_: Added support for configuration option aliases via the ``aliases`` parameter in :meth:`Parser.addini() &lt;pytest.Parser.addini&gt;`.

Plugins can now register alternative names for configuration options,
allowing for more flexibility in configuration naming and supporting backward compatibility when renaming options.
The canonical name always takes precedence if both the canonical name and an alias are specified in the configuration file.



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

- `13330 &lt;https://github.com/pytest-dev/pytest/issues/13330&gt;`_: Having pytest configuration spread over more than one file (for example having both a ``pytest.ini`` file and ``pyproject.toml`` with a ``[tool.pytest.ini_options]`` table) will now print a warning to make it clearer to the user that only one of them is actually used.

-- by :user:`sgaist`


- `13574 &lt;https://github.com/pytest-dev/pytest/issues/13574&gt;`_: The single argument ``--version`` no longer loads the entire plugin infrastructure, making it faster and more reliable when displaying only the pytest version.

Passing ``--version`` twice (e.g., ``pytest --version --version``) retains the original behavior, showing both the pytest version and plugin information.

.. note::

   Since ``--version`` is now processed early, it only takes effect when passed directly via the command line. It will not work if set through other mechanisms, such as :envvar:`PYTEST_ADDOPTS` or :confval:`addopts`.


- `13823 &lt;https://github.com/pytest-dev/pytest/issues/13823&gt;`_: Added :confval:`strict_xfail` as an alias to the ``xfail_strict`` option,
:confval:`strict_config` as an alias to the ``--strict-config`` flag,
and :confval:`strict_markers` as an alias to the ``--strict-markers`` flag.
This makes all strictness options consistently have configuration options with the prefix ``strict_``.

- `13700 &lt;https://github.com/pytest-dev/pytest/issues/13700&gt;`_: `--junitxml`  no longer prints the `generated xml file` summary at the end of the pytest session when `--quiet` is given.


- `13732 &lt;https://github.com/pytest-dev/pytest/issues/13732&gt;`_: Previously, when filtering warnings, pytest would fail if the filter referenced a class that could not be imported. Now, this only outputs a message indicating the problem.


- `13859 &lt;https://github.com/pytest-dev/pytest/issues/13859&gt;`_: Clarify the error message for `pytest.raises()` when a regex `match` fails.


- `13861 &lt;https://github.com/pytest-dev/pytest/issues/13861&gt;`_: Better sentence structure in a test&#x27;s expected error message. Previously, the error message would be &quot;expected exception must be &lt;expected&gt;, but got &lt;actual&gt;&quot;. Now, it is &quot;Expected &lt;expected&gt;, but got &lt;actual&gt;&quot;.


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

- `12083 &lt;https://github.com/pytest-dev/pytest/issues/12083&gt;`_: Fixed a bug where an invocation such as `pytest a/ a/b` would cause only tests from `a/b` to run, and not other tests under `a/`.

The fix entails a few breaking changes to how such overlapping arguments and duplicates are handled:

1. `pytest a/b a/` or `pytest a/ a/b` are equivalent to `pytest a`; if an argument overlaps another arguments, only the prefix remains.

2. `pytest x.py x.py` is equivalent to `pytest x.py`; previously such an invocation was taken as an explicit request to run the tests from the file twice.

If you rely on these behaviors, consider using :ref:`--keep-duplicates &lt;duplicate-paths&gt;`, which retains its existing behavior (including the bug).


- `13719 &lt;https://github.com/pytest-dev/pytest/issues/13719&gt;`_: Support for Python 3.9 is dropped following its end of life.


- `13766 &lt;https://github.com/pytest-dev/pytest/issues/13766&gt;`_: Previously, pytest would assume it was running in a CI/CD environment if either of the environment variables `$CI` or `$BUILD_NUMBER` was defined;
now, CI mode is only activated if at least one of those variables is defined and set to a *non-empty* value.


- `13779 &lt;https://github.com/pytest-dev/pytest/issues/13779&gt;`_: **PytestRemovedIn9Warning deprecation warnings are now errors by default.**

Following our plan to remove deprecated features with as little disruption as
possible, all warnings of type ``PytestRemovedIn9Warning`` now generate errors
instead of warning messages by default.

**The affected features will be effectively removed in pytest 9.1**, so please consult the
:ref:`deprecations` section in the docs for directions on how to update existing code.

In the pytest ``9.0.X`` series, it is possible to change the errors back into warnings as a
stopgap measure by adding this to your ``pytest.ini`` file:

.. code-block:: ini

   [pytest]
   filterwarnings =
       ignore::pytest.PytestRemovedIn9Warning

But this will stop working when pytest ``9.1`` is released.

**If you have concerns** about the removal of a specific feature, please add a
comment to :issue:`13779`.



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

- `13807 &lt;https://github.com/pytest-dev/pytest/issues/13807&gt;`_: :meth:`monkeypatch.syspath_prepend() &lt;pytest.MonkeyPatch.syspath_prepend&gt;` now issues a deprecation warning when the prepended path contains legacy namespace packages (those using ``pkg_resources.declare_namespace()``).
Users should migrate to native namespace packages (:pep:`420`).
See :ref:`monkeypatch-fixup-namespace-packages` for details.


Bug fixes
---------

- `13445 &lt;https://github.com/pytest-dev/pytest/issues/13445&gt;`_: Made the type annotations of :func:`pytest.skip` and friends more spec-complaint to have them work across more type checkers.


- `13537 &lt;https://github.com/pytest-dev/pytest/issues/13537&gt;`_: Fixed a bug in which :class:`ExceptionGroup` with only ``Skipped`` exceptions in teardown was not handled correctly and showed as error.


- `13598 &lt;https://github.com/pytest-dev/pytest/issues/13598&gt;`_: Fixed possible collection confusion on Windows when short paths and symlinks are involved.


- `13716 &lt;https://github.com/pytest-dev/pytest/issues/13716&gt;`_: Fixed a bug where a nonsensical invocation like ``pytest x.py[a]`` (a file cannot be parametrized) was silently treated as ``pytest x.py``. This is now a usage error.


- `13722 &lt;https://github.com/pytest-dev/pytest/issues/13722&gt;`_: Fixed a misleading assertion failure message when using :func:`pytest.approx` on mappings with differing lengths.


- `13773 &lt;https://github.com/pytest-dev/pytest/issues/13773&gt;`_: Fixed the static fixture closure calculation to properly consider transitive dependencies requested by overridden fixtures.


- `13816 &lt;https://github.com/pytest-dev/pytest/issues/13816&gt;`_: Fixed :func:`pytest.approx` which now returns a clearer error message when comparing mappings with different keys.


- `13849 &lt;https://github.com/pytest-dev/pytest/issues/13849&gt;`_: Hidden ``.pytest.ini`` files are now picked up as the config file even if empty.
This was an inconsistency with non-hidden ``pytest.ini``.


- `13865 &lt;https://github.com/pytest-dev/pytest/issues/13865&gt;`_: Fixed `--show-capture` with `--tb=line`.


- `13522 &lt;https://github.com/pytest-dev/pytest/issues/13522&gt;`_: Fixed :fixture:`pytester` in subprocess mode ignored all :attr`pytester.plugins &lt;pytest.Pytester.plugins&gt;` except the first.

Fixed :fixture:`pytester` in subprocess mode silently ignored non-str :attr:`pytester.plugins &lt;pytest.Pytester.plugins&gt;`.
Now it errors instead.
If you are affected by this, specify the plugin by name, or switch the affected tests to use :func:`pytester.runpytest_inprocess &lt;pytest.Pytester.runpytest_inprocess&gt;` explicitly instead.



Packaging updates and notes for downstreams
-------------------------------------------

- `13791 &lt;https://github.com/pytest-dev/pytest/issues/13791&gt;`_: Minimum requirements on ``iniconfig`` and ``packaging`` were bumped to ``1.0.1`` and ``22.0.0``, respectively.



Contributor-facing changes
--------------------------

- `12244 &lt;https://github.com/pytest-dev/pytest/issues/12244&gt;`_: Fixed self-test failures when `TERM=dumb`.


- `12474 &lt;https://github.com/pytest-dev/pytest/issues/12474&gt;`_: Added scheduled GitHub Action Workflow to run Sphinx linkchecks in repo documentation.


- `13621 &lt;https://github.com/pytest-dev/pytest/issues/13621&gt;`_: pytest&#x27;s own testsuite now handles the ``lsof`` command hanging (e.g. due to unreachable network filesystems), with the affected selftests being skipped after 10 seconds.


- `13638 &lt;https://github.com/pytest-dev/pytest/issues/13638&gt;`_: Fixed deprecated :command:`gh pr new` command in :file:`scripts/prepare-release-pr.py`.
The script now uses :command:`gh pr create` which is compatible with GitHub CLI v2.0+.


- `13695 &lt;https://github.com/pytest-dev/pytest/issues/13695&gt;`_: Flush `stdout` and `stderr` in `Pytester.run` to avoid truncated outputs in `test_faulthandler.py::test_timeout` on CI -- by :user:`ogrisel`.


- `13771 &lt;https://github.com/pytest-dev/pytest/issues/13771&gt;`_: Skip `test_do_not_collect_symlink_siblings` on Windows environments without symlink support to avoid false negatives.


- `13841 &lt;https://github.com/pytest-dev/pytest/issues/13841&gt;`_: ``tox&gt;=4`` is now required when contributing to pytest.

- `13625 &lt;https://github.com/pytest-dev/pytest/issues/13625&gt;`_: Added missing docstrings to ``pytest_addoption()``, ``pytest_configure()``, and ``cacheshow()`` functions in ``cacheprovider.py``.



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

- `13830 &lt;https://github.com/pytest-dev/pytest/issues/13830&gt;`_: Configuration overrides (``-o``/``--override-ini``) are now processed during startup rather than during :func:`config.getini() &lt;pytest.Config.getini&gt;`.

8.4.2

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

Bug fixes
---------

- `13478 &lt;https://github.com/pytest-dev/pytest/issues/13478&gt;`_: Fixed a crash when using :confval:`console_output_style` with ``times`` and a module is skipped.


- `13530 &lt;https://github.com/pytest-dev/pytest/issues/13530&gt;`_: Fixed a crash when using :func:`pytest.approx` and :class:`decimal.Decimal` instances with the :class:`decimal.FloatOperation` trap set.


- `13549 &lt;https://github.com/pytest-dev/pytest/issues/13549&gt;`_: No longer evaluate type annotations in Python ``3.14`` when inspecting function signatures.

This prevents crashes during module collection when modules do not explicitly use ``from __future__ import annotations`` and import types for annotations within a ``if TYPE_CHECKING:`` block.


- `13559 &lt;https://github.com/pytest-dev/pytest/issues/13559&gt;`_: Added missing `int` and `float` variants to the `Literal` type annotation of the `type` parameter in :meth:`pytest.Parser.addini`.


- `13563 &lt;https://github.com/pytest-dev/pytest/issues/13563&gt;`_: :func:`pytest.approx` now only imports ``numpy`` if NumPy is already in ``sys.modules``. This fixes unconditional import behavior introduced in `8.4.0`.



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

- `13577 &lt;https://github.com/pytest-dev/pytest/issues/13577&gt;`_: Clarify that ``pytest_generate_tests`` is discovered in test modules/classes; other hooks must be in ``conftest.py`` or plugins.



Contributor-facing changes
--------------------------

- `13480 &lt;https://github.com/pytest-dev/pytest/issues/13480&gt;`_: Self-testing: fixed a few test failures when run with ``-Wdefault`` or a similar override.


- `13547 &lt;https://github.com/pytest-dev/pytest/issues/13547&gt;`_: Self-testing: corrected expected message for ``test_doctest_unexpected_exception`` in Python ``3.14``.


- `13684 &lt;https://github.com/pytest-dev/pytest/issues/13684&gt;`_: Make pytest&#x27;s own testsuite insensitive to the presence of the ``CI`` environment variable -- by :user:`ogrisel`.

Links

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

Update tomli from 2.2.1 to 2.3.0.

Changelog

2.3.0

- Added
- Binary wheels for Python 3.14 (also free-threaded)
- Performance

pyup-bot · 2025-11-24T18:01:41Z

Closing this in favor of #407

pyup-bot added 18 commits November 10, 2025 15:48

Update attrs from 25.3.0 to 25.4.0

bac3e02

Update cattrs from 25.1.1 to 25.3.0

f0e3592

Update fonttools from 4.59.0 to 4.60.1

180cca4

Update lxml from 6.0.0 to 6.0.2

533a144

Update msgpack from 1.1.1 to 1.1.2

243c4b9

Update orjson from 3.11.0 to 3.11.4

5c89551

Update typing-extensions from 4.14.1 to 4.15.0

3f14fd6

Update typing-extensions from 4.14.1 to 4.15.0

3a9b64f

Update black from 25.1.0 to 25.11.0

e7d2bd4

Update click from 8.1.8 to 8.3.0

f0c31cf

Update click from 8.2.1 to 8.3.0

b9238a2

Update coverage from 7.9.2 to 7.11.3

fd7ae7b

Update iniconfig from 2.1.0 to 2.3.0

d736027

Update isort from 6.0.1 to 7.0.0

8d836fc

Update mypy from 1.17.0 to 1.18.2

3f5461e

Update platformdirs from 4.3.8 to 4.5.0

9a07e98

Update pytest from 8.4.1 to 9.0.0

4673283

Update tomli from 2.2.1 to 2.3.0

763c753

pyup-bot mentioned this pull request Nov 10, 2025

Scheduled weekly dependency update for week 44 #405

Closed

pyup-bot closed this Nov 24, 2025

madig deleted the pyup-scheduled-update-2025-11-10 branch November 24, 2025 18:01

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Scheduled weekly dependency update for week 45#406

Scheduled weekly dependency update for week 45#406
pyup-bot wants to merge 18 commits into
mainfrom
pyup-scheduled-update-2025-11-10

pyup-bot commented Nov 10, 2025

Uh oh!

pyup-bot commented Nov 24, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

pyup-bot commented Nov 10, 2025

Update attrs from 25.3.0 to 25.4.0.

Update cattrs from 25.1.1 to 25.3.0.

25.3.0

25.2.0

Update fonttools from 4.59.0 to 4.60.1.

4.60.1

4.60.0

4.59.2

4.59.1

Update lxml from 6.0.0 to 6.0.2.

6.0.2

6.0.1

Update msgpack from 1.1.1 to 1.1.2.

1.1.2

Update orjson from 3.11.0 to 3.11.4.

3.11.4

3.11.3

3.11.2

3.11.1

Update typing-extensions from 4.14.1 to 4.15.0.

4.15.0

4.15.0rc1

Update black from 25.1.0 to 25.11.0.

25.11.0

25.9.0

Update click from 8.1.8 to 8.3.0.

8.3.0

8.2.2

8.2.1

8.2.0

Update coverage from 7.9.2 to 7.11.3.

7.11.3

7.11.2

7.11.1

7.11.0

7.10.7

7.10.6

7.10.5

7.10.4

7.10.3

7.10.2

7.10.1

7.10.0

Update iniconfig from 2.1.0 to 2.3.0.

2.2.0

Update isort from 6.0.1 to 7.0.0.

6.1.0

Update mypy from 1.17.0 to 1.18.2.

1.18.2

1.18.1

1.17.1

Update platformdirs from 4.3.8 to 4.5.0.

Update pytest from 8.4.1 to 9.0.0.

9.0.0

8.4.2

Update tomli from 2.2.1 to 2.3.0.

2.3.0

Uh oh!

pyup-bot commented Nov 24, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant