search

justvanrossum / fontgoggles

FontGoggles: Visual OTL Preview and QA
Apache License 2.0
399 stars 42 forks source link

Scheduled weekly dependency update for week 16 #403

Closed pyup-bot closed 5 months ago

pyup-bot commented 5 months ago

Update pytest from 7.2.2 to 8.1.1.

Changelog ### 8.1.0 ``` ===================== .. note:: This release has been **yanked**: it broke some plugins without the proper warning period, due to some warnings not showing up as expected. See `12069 <https://github.com/pytest-dev/pytest/issues/12069>`__. Features -------- - `11475 <https://github.com/pytest-dev/pytest/issues/11475>`_: Added the new :confval:`consider_namespace_packages` configuration option, defaulting to ``False``. If set to ``True``, pytest will attempt to identify modules that are part of `namespace packages <https://packaging.python.org/en/latest/guides/packaging-namespace-packages>`__ when importing modules. - `11653 <https://github.com/pytest-dev/pytest/issues/11653>`_: Added the new :confval:`verbosity_test_cases` configuration option for fine-grained control of test execution verbosity. See :ref:`Fine-grained verbosity <pytest.fine_grained_verbosity>` for more details. Improvements ------------ - `10865 <https://github.com/pytest-dev/pytest/issues/10865>`_: :func:`pytest.warns` now validates that :func:`warnings.warn` was called with a `str` or a `Warning`. Currently in Python it is possible to use other types, however this causes an exception when :func:`warnings.filterwarnings` is used to filter those warnings (see `CPython 103577 <https://github.com/python/cpython/issues/103577>`__ for a discussion). While this can be considered a bug in CPython, we decided to put guards in pytest as the error message produced without this check in place is confusing. - `11311 <https://github.com/pytest-dev/pytest/issues/11311>`_: When using ``--override-ini`` for paths in invocations without a configuration file defined, the current working directory is used as the relative directory. Previoulsy this would raise an :class:`AssertionError`. - `11475 <https://github.com/pytest-dev/pytest/issues/11475>`_: :ref:`--import-mode=importlib <import-mode-importlib>` now tries to import modules using the standard import mechanism (but still without changing :py:data:`sys.path`), falling back to importing modules directly only if that fails. This means that installed packages will be imported under their canonical name if possible first, for example ``app.core.models``, instead of having the module name always be derived from their path (for example ``.env310.lib.site_packages.app.core.models``). - `11801 <https://github.com/pytest-dev/pytest/issues/11801>`_: Added the :func:`iter_parents() <_pytest.nodes.Node.iter_parents>` helper method on nodes. It is similar to :func:`listchain <_pytest.nodes.Node.listchain>`, but goes from bottom to top, and returns an iterator, not a list. - `11850 <https://github.com/pytest-dev/pytest/issues/11850>`_: Added support for :data:`sys.last_exc` for post-mortem debugging on Python>=3.12. - `11962 <https://github.com/pytest-dev/pytest/issues/11962>`_: In case no other suitable candidates for configuration file are found, a ``pyproject.toml`` (even without a ``[tool.pytest.ini_options]`` table) will be considered as the configuration file and define the ``rootdir``. - `11978 <https://github.com/pytest-dev/pytest/issues/11978>`_: Add ``--log-file-mode`` option to the logging plugin, enabling appending to log-files. This option accepts either ``"w"`` or ``"a"`` and defaults to ``"w"``. Previously, the mode was hard-coded to be ``"w"`` which truncates the file before logging. - `12047 <https://github.com/pytest-dev/pytest/issues/12047>`_: When multiple finalizers of a fixture raise an exception, now all exceptions are reported as an exception group. Previously, only the first exception was reported. Bug Fixes --------- - `11904 <https://github.com/pytest-dev/pytest/issues/11904>`_: Fixed a regression in pytest 8.0.0 that would cause test collection to fail due to permission errors when using ``--pyargs``. This change improves the collection tree for tests specified using ``--pyargs``, see :pull:`12043` for a comparison with pytest 8.0 and <8. - `12011 <https://github.com/pytest-dev/pytest/issues/12011>`_: Fixed a regression in 8.0.1 whereby ``setup_module`` xunit-style fixtures are not executed when ``--doctest-modules`` is passed. - `12014 <https://github.com/pytest-dev/pytest/issues/12014>`_: Fix the ``stacklevel`` used when warning about marks used on fixtures. - `12039 <https://github.com/pytest-dev/pytest/issues/12039>`_: Fixed a regression in ``8.0.2`` where tests created using :fixture:`tmp_path` have been collected multiple times in CI under Windows. Improved Documentation ---------------------- - `11790 <https://github.com/pytest-dev/pytest/issues/11790>`_: Documented the retention of temporary directories created using the ``tmp_path`` fixture in more detail. Trivial/Internal Changes ------------------------ - `11785 <https://github.com/pytest-dev/pytest/issues/11785>`_: Some changes were made to private functions which may affect plugins which access them: - ``FixtureManager._getautousenames()`` now takes a ``Node`` itself instead of the nodeid. - ``FixtureManager.getfixturedefs()`` now takes the ``Node`` itself instead of the nodeid. - The ``_pytest.nodes.iterparentnodeids()`` function is removed without replacement. Prefer to traverse the node hierarchy itself instead. If you really need to, copy the function from the previous pytest release. ``` ### 8.0.2 ``` ========================= Bug Fixes --------- - `11895 <https://github.com/pytest-dev/pytest/issues/11895>`_: Fix collection on Windows where initial paths contain the short version of a path (for example ``c:\PROGRA~1\tests``). - `11953 <https://github.com/pytest-dev/pytest/issues/11953>`_: Fix an ``IndexError`` crash raising from ``getstatementrange_ast``. - `12021 <https://github.com/pytest-dev/pytest/issues/12021>`_: Reverted a fix to `--maxfail` handling in pytest 8.0.0 because it caused a regression in pytest-xdist whereby session fixture teardowns may get executed multiple times when the max-fails is reached. ``` ### 8.0.1 ``` ========================= Bug Fixes --------- - `11875 <https://github.com/pytest-dev/pytest/issues/11875>`_: Correctly handle errors from :func:`getpass.getuser` in Python 3.13. - `11879 <https://github.com/pytest-dev/pytest/issues/11879>`_: Fix an edge case where ``ExceptionInfo._stringify_exception`` could crash :func:`pytest.raises`. - `11906 <https://github.com/pytest-dev/pytest/issues/11906>`_: Fix regression with :func:`pytest.warns` using custom warning subclasses which have more than one parameter in their `__init__`. - `11907 <https://github.com/pytest-dev/pytest/issues/11907>`_: Fix a regression in pytest 8.0.0 whereby calling :func:`pytest.skip` and similar control-flow exceptions within a :func:`pytest.warns()` block would get suppressed instead of propagating. - `11929 <https://github.com/pytest-dev/pytest/issues/11929>`_: Fix a regression in pytest 8.0.0 whereby autouse fixtures defined in a module get ignored by the doctests in the module. - `11937 <https://github.com/pytest-dev/pytest/issues/11937>`_: Fix a regression in pytest 8.0.0 whereby items would be collected in reverse order in some circumstances. ``` ### 8.0.0 ``` ========================= Bug Fixes --------- - `11842 <https://github.com/pytest-dev/pytest/issues/11842>`_: Properly escape the ``reason`` of a :ref:`skip <pytest.mark.skip ref>` mark when writing JUnit XML files. - `11861 <https://github.com/pytest-dev/pytest/issues/11861>`_: Avoid microsecond exceeds ``1_000_000`` when using ``log-date-format`` with ``%f`` specifier, which might cause the test suite to crash. ``` ### 8.0.0rc2 ``` ============================ Improvements ------------ - `11233 <https://github.com/pytest-dev/pytest/issues/11233>`_: Improvements to ``-r`` for xfailures and xpasses: * Report tracebacks for xfailures when ``-rx`` is set. * Report captured output for xpasses when ``-rX`` is set. * For xpasses, add ``-`` in summary between test name and reason, to match how xfail is displayed. - `11825 <https://github.com/pytest-dev/pytest/issues/11825>`_: The :hook:`pytest_plugin_registered` hook has a new ``plugin_name`` parameter containing the name by which ``plugin`` is registered. Bug Fixes --------- - `11706 <https://github.com/pytest-dev/pytest/issues/11706>`_: Fix reporting of teardown errors in higher-scoped fixtures when using `--maxfail` or `--stepwise`. NOTE: This change was reverted in pytest 8.0.2 to fix a `regression <https://github.com/pytest-dev/pytest-xdist/issues/1024>`_ it caused in pytest-xdist. - `11758 <https://github.com/pytest-dev/pytest/issues/11758>`_: Fixed ``IndexError: string index out of range`` crash in ``if highlighted[-1] == "\n" and source[-1] != "\n"``. This bug was introduced in pytest 8.0.0rc1. - `9765 <https://github.com/pytest-dev/pytest/issues/9765>`_, `#11816 <https://github.com/pytest-dev/pytest/issues/11816>`_: Fixed a frustrating bug that afflicted some users with the only error being ``assert mod not in mods``. The issue was caused by the fact that ``str(Path(mod))`` and ``mod.__file__`` don't necessarily produce the same string, and was being erroneously used interchangably in some places in the code. This fix also broke the internal API of ``PytestPluginManager.consider_conftest`` by introducing a new parameter -- we mention this in case it is being used by external code, even if marked as *private*. ``` ### 8.0.0rc1 ``` ============================ Breaking Changes ---------------- Old Deprecations Are Now Errors ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - `7363 <https://github.com/pytest-dev/pytest/issues/7363>`_: **PytestRemovedIn8Warning deprecation warnings are now errors by default.** Following our plan to remove deprecated features with as little disruption as possible, all warnings of type ``PytestRemovedIn8Warning`` now generate errors instead of warning messages by default. **The affected features will be effectively removed in pytest 8.1**, so please consult the :ref:`deprecations` section in the docs for directions on how to update existing code. In the pytest ``8.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.PytestRemovedIn8Warning But this will stop working when pytest ``8.1`` is released. **If you have concerns** about the removal of a specific feature, please add a comment to :issue:`7363`. Version Compatibility ^^^^^^^^^^^^^^^^^^^^^ - `11151 <https://github.com/pytest-dev/pytest/issues/11151>`_: Dropped support for Python 3.7, which `reached end-of-life on 2023-06-27 <https://devguide.python.org/versions/>`__. - ``pluggy>=1.3.0`` is now required. Collection Changes ^^^^^^^^^^^^^^^^^^ In this version we've made several breaking changes to pytest's collection phase, particularly around how filesystem directories and Python packages are collected, fixing deficiencies and allowing for cleanups and improvements to pytest's internals. A deprecation period for these changes was not possible. - `7777 <https://github.com/pytest-dev/pytest/issues/7777>`_: Files and directories are now collected in alphabetical order jointly, unless changed by a plugin. Previously, files were collected before directories. See below for an example. - `8976 <https://github.com/pytest-dev/pytest/issues/8976>`_: Running `pytest pkg/__init__.py` now collects the `pkg/__init__.py` file (module) only. Previously, it collected the entire `pkg` package, including other test files in the directory, but excluding tests in the `__init__.py` file itself (unless :confval:`python_files` was changed to allow `__init__.py` file). To collect the entire package, specify just the directory: `pytest pkg`. - `11137 <https://github.com/pytest-dev/pytest/issues/11137>`_: :class:`pytest.Package` is no longer a :class:`pytest.Module` or :class:`pytest.File`. The ``Package`` collector node designates a Python package, that is, a directory with an `__init__.py` file. Previously ``Package`` was a subtype of ``pytest.Module`` (which represents a single Python module), the module being the `__init__.py` file. This has been deemed a design mistake (see :issue:`11137` and :issue:`7777` for details). The ``path`` property of ``Package`` nodes now points to the package directory instead of the ``__init__.py`` file. Note that a ``Module`` node for ``__init__.py`` (which is not a ``Package``) may still exist, if it is picked up during collection (e.g. if you configured :confval:`python_files` to include ``__init__.py`` files). - `7777 <https://github.com/pytest-dev/pytest/issues/7777>`_: Added a new :class:`pytest.Directory` base collection node, which all collector nodes for filesystem directories are expected to subclass. This is analogous to the existing :class:`pytest.File` for file nodes. Changed :class:`pytest.Package` to be a subclass of :class:`pytest.Directory`. A ``Package`` represents a filesystem directory which is a Python package, i.e. contains an ``__init__.py`` file. :class:`pytest.Package` now only collects files in its own directory; previously it collected recursively. Sub-directories are collected as their own collector nodes, which then collect themselves, thus creating a collection tree which mirrors the filesystem hierarchy. Added a new :class:`pytest.Dir` concrete collection node, a subclass of :class:`pytest.Directory`. This node represents a filesystem directory, which is not a :class:`pytest.Package`, that is, does not contain an ``__init__.py`` file. Similarly to ``Package``, it only collects the files in its own directory. :class:`pytest.Session` now only collects the initial arguments, without recursing into directories. This work is now done by the :func:`recursive expansion process <pytest.Collector.collect>` of directory collector nodes. :attr:`session.name <pytest.Session.name>` is now ``""``; previously it was the rootdir directory name. This matches :attr:`session.nodeid <_pytest.nodes.Node.nodeid>` which has always been `""`. The collection tree now contains directories/packages up to the :ref:`rootdir <rootdir>`, for initial arguments that are found within the rootdir. For files outside the rootdir, only the immediate directory/package is collected -- note however that collecting from outside the rootdir is discouraged. As an example, given the following filesystem tree:: myroot/ pytest.ini top/ ├── aaa │ └── test_aaa.py ├── test_a.py ├── test_b │ ├── __init__.py │ └── test_b.py ├── test_c.py └── zzz ├── __init__.py └── test_zzz.py the collection tree, as shown by `pytest --collect-only top/` but with the otherwise-hidden :class:`~pytest.Session` node added for clarity, is now the following:: <Session> <Dir myroot> <Dir top> <Dir aaa> <Module test_aaa.py> <Function test_it> <Module test_a.py> <Function test_it> <Package test_b> <Module test_b.py> <Function test_it> <Module test_c.py> <Function test_it> <Package zzz> <Module test_zzz.py> <Function test_it> Previously, it was:: <Session> <Module top/test_a.py> <Function test_it> <Module top/test_c.py> <Function test_it> <Module top/aaa/test_aaa.py> <Function test_it> <Package test_b> <Module test_b.py> <Function test_it> <Package zzz> <Module test_zzz.py> <Function test_it> Code/plugins which rely on a specific shape of the collection tree might need to update. - `11676 <https://github.com/pytest-dev/pytest/issues/11676>`_: The classes :class:`~_pytest.nodes.Node`, :class:`~pytest.Collector`, :class:`~pytest.Item`, :class:`~pytest.File`, :class:`~_pytest.nodes.FSCollector` are now marked abstract (see :mod:`abc`). We do not expect this change to affect users and plugin authors, it will only cause errors when the code is already wrong or problematic. Other breaking changes ^^^^^^^^^^^^^^^^^^^^^^ These are breaking changes where deprecation was not possible. - `11282 <https://github.com/pytest-dev/pytest/issues/11282>`_: Sanitized the handling of the ``default`` parameter when defining configuration options. Previously if ``default`` was not supplied for :meth:`parser.addini <pytest.Parser.addini>` and the configuration option value was not defined in a test session, then calls to :func:`config.getini <pytest.Config.getini>` returned an *empty list* or an *empty string* depending on whether ``type`` was supplied or not respectively, which is clearly incorrect. Also, ``None`` was not honored even if ``default=None`` was used explicitly while defining the option. Now the behavior of :meth:`parser.addini <pytest.Parser.addini>` is as follows: * If ``default`` is NOT passed but ``type`` is provided, then a type-specific default will be returned. For example ``type=bool`` will return ``False``, ``type=str`` will return ``""``, etc. * If ``default=None`` is passed and the option is not defined in a test session, then ``None`` will be returned, regardless of the ``type``. * If neither ``default`` nor ``type`` are provided, assume ``type=str`` and return ``""`` as default (this is as per previous behavior). The team decided to not introduce a deprecation period for this change, as doing so would be complicated both in terms of communicating this to the community as well as implementing it, and also because the team believes this change should not break existing plugins except in rare cases. - `11667 <https://github.com/pytest-dev/pytest/issues/11667>`_: pytest's ``setup.py`` file is removed. If you relied on this file, e.g. to install pytest using ``setup.py install``, please see `Why you shouldn't invoke setup.py directly <https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html#summary>`_ for alternatives. - `9288 <https://github.com/pytest-dev/pytest/issues/9288>`_: :func:`~pytest.warns` now re-emits unmatched warnings when the context closes -- previously it would consume all warnings, hiding those that were not matched by the function. While this is a new feature, we announce it as a breaking change because many test suites are configured to error-out on warnings, and will therefore fail on the newly-re-emitted warnings. - The internal ``FixtureManager.getfixtureclosure`` method has changed. Plugins which use this method or which subclass ``FixtureManager`` and overwrite that method will need to adapt to the change. Deprecations ------------ - `10465 <https://github.com/pytest-dev/pytest/issues/10465>`_: Test functions returning a value other than ``None`` will now issue a :class:`pytest.PytestWarning` instead of ``pytest.PytestRemovedIn8Warning``, meaning this will stay a warning instead of becoming an error in the future. - `3664 <https://github.com/pytest-dev/pytest/issues/3664>`_: Applying a mark to a fixture function now issues a warning: marks in fixtures never had any effect, but it is a common user error to apply a mark to a fixture (for example ``usefixtures``) and expect it to work. This will become an error in pytest 9.0. Features and Improvements ------------------------- Improved Diffs ^^^^^^^^^^^^^^ These changes improve the diffs that pytest prints when an assertion fails. Note that syntax highlighting requires the ``pygments`` package. - `11520 <https://github.com/pytest-dev/pytest/issues/11520>`_: The very verbose (``-vv``) diff output is now colored as a diff instead of a big chunk of red. Python code in error reports is now syntax-highlighted as Python. The sections in the error reports are now better separated. - `1531 <https://github.com/pytest-dev/pytest/issues/1531>`_: The very verbose diff (``-vv``) for every standard library container type is improved. The indentation is now consistent and the markers are on their own separate lines, which should reduce the diffs shown to users. Previously, the standard Python pretty printer was used to generate the output, which puts opening and closing markers on the same line as the first/last entry, in addition to not having consistent indentation. - `10617 <https://github.com/pytest-dev/pytest/issues/10617>`_: Added more comprehensive set assertion rewrites for comparisons other than equality ``==``, with the following operations now providing better failure messages: ``!=``, ``<=``, ``>=``, ``<``, and ``>``. Separate Control For Assertion Verbosity ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - `11387 <https://github.com/pytest-dev/pytest/issues/11387>`_: Added the new :confval:`verbosity_assertions` configuration option for fine-grained control of failed assertions verbosity. If you've ever wished that pytest always show you full diffs, but without making everything else verbose, this is for you. See :ref:`Fine-grained verbosity <pytest.fine_grained_verbosity>` for more details. For plugin authors, :attr:`config.get_verbosity <pytest.Config.get_verbosity>` can be used to retrieve the verbosity level for a specific verbosity type. Additional Support For Exception Groups and ``__notes__`` ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ These changes improve pytest's support for exception groups. - `10441 <https://github.com/pytest-dev/pytest/issues/10441>`_: Added :func:`ExceptionInfo.group_contains() <pytest.ExceptionInfo.group_contains>`, an assertion helper that tests if an :class:`ExceptionGroup` contains a matching exception. See :ref:`assert-matching-exception-groups` for an example. - `11227 <https://github.com/pytest-dev/pytest/issues/11227>`_: Allow :func:`pytest.raises` ``match`` argument to match against `PEP-678 <https://peps.python.org/pep-0678/>` ``__notes__``. Custom Directory collectors ^^^^^^^^^^^^^^^^^^^^^^^^^^^ - `7777 <https://github.com/pytest-dev/pytest/issues/7777>`_: Added a new hook :hook:`pytest_collect_directory`, which is called by filesystem-traversing collector nodes, such as :class:`pytest.Session`, :class:`pytest.Dir` and :class:`pytest.Package`, to create a collector node for a sub-directory. It is expected to return a subclass of :class:`pytest.Directory`. This hook allows plugins to :ref:`customize the collection of directories <custom directory collectors>`. "New-style" Hook Wrappers ^^^^^^^^^^^^^^^^^^^^^^^^^ - `11122 <https://github.com/pytest-dev/pytest/issues/11122>`_: pytest now uses "new-style" hook wrappers internally, available since pluggy 1.2.0. See `pluggy's 1.2.0 changelog <https://pluggy.readthedocs.io/en/latest/changelog.html#pluggy-1-2-0-2023-06-21>`_ and the :ref:`updated docs <hookwrapper>` for details. Plugins which want to use new-style wrappers can do so if they require ``pytest>=8``. Other Improvements ^^^^^^^^^^^^^^^^^^ - `11216 <https://github.com/pytest-dev/pytest/issues/11216>`_: If a test is skipped from inside an :ref:`xunit setup fixture <classic xunit>`, the test summary now shows the test location instead of the fixture location. - `11314 <https://github.com/pytest-dev/pytest/issues/11314>`_: Logging to a file using the ``--log-file`` option will use ``--log-level``, ``--log-format`` and ``--log-date-format`` as fallback if ``--log-file-level``, ``--log-file-format`` and ``--log-file-date-format`` are not provided respectively. - `11610 <https://github.com/pytest-dev/pytest/issues/11610>`_: Added the :func:`LogCaptureFixture.filtering() <pytest.LogCaptureFixture.filtering>` context manager which adds a given :class:`logging.Filter` object to the :fixture:`caplog` fixture. - `11447 <https://github.com/pytest-dev/pytest/issues/11447>`_: :func:`pytest.deprecated_call` now also considers warnings of type :class:`FutureWarning`. - `11600 <https://github.com/pytest-dev/pytest/issues/11600>`_: Improved the documentation and type signature for :func:`pytest.mark.xfail <pytest.mark.xfail>`'s ``condition`` param to use ``False`` as the default value. - `7469 <https://github.com/pytest-dev/pytest/issues/7469>`_: :class:`~pytest.FixtureDef` is now exported as ``pytest.FixtureDef`` for typing purposes. - `11353 <https://github.com/pytest-dev/pytest/issues/11353>`_: Added typing to :class:`~pytest.PytestPluginManager`. Bug Fixes --------- - `10701 <https://github.com/pytest-dev/pytest/issues/10701>`_: :meth:`pytest.WarningsRecorder.pop` will return the most-closely-matched warning in the list, rather than the first warning which is an instance of the requested type. - `11255 <https://github.com/pytest-dev/pytest/issues/11255>`_: Fixed crash on `parametrize(..., scope="package")` without a package present. - `11277 <https://github.com/pytest-dev/pytest/issues/11277>`_: Fixed a bug that when there are multiple fixtures for an indirect parameter, the scope of the highest-scope fixture is picked for the parameter set, instead of that of the one with the narrowest scope. - `11456 <https://github.com/pytest-dev/pytest/issues/11456>`_: Parametrized tests now *really do* ensure that the ids given to each input are unique - for example, ``a, a, a0`` now results in ``a1, a2, a0`` instead of the previous (buggy) ``a0, a1, a0``. This necessarily means changing nodeids where these were previously colliding, and for readability adds an underscore when non-unique ids end in a number. - `11563 <https://github.com/pytest-dev/pytest/issues/11563>`_: Fixed a crash when using an empty string for the same parametrized value more than once. - `11712 <https://github.com/pytest-dev/pytest/issues/11712>`_: Fixed handling ``NO_COLOR`` and ``FORCE_COLOR`` to ignore an empty value. - `9036 <https://github.com/pytest-dev/pytest/issues/9036>`_: ``pytest.warns`` and similar functions now capture warnings when an exception is raised inside a ``with`` block. Improved Documentation ---------------------- - `11011 <https://github.com/pytest-dev/pytest/issues/11011>`_: Added a warning about modifying the root logger during tests when using ``caplog``. - `11065 <https://github.com/pytest-dev/pytest/issues/11065>`_: Use ``pytestconfig`` instead of ``request.config`` in cache example to be consistent with the API documentation. Trivial/Internal Changes ------------------------ - `11208 <https://github.com/pytest-dev/pytest/issues/11208>`_: The (internal) ``FixtureDef.cached_result`` type has changed. Now the third item ``cached_result[2]``, when set, is an exception instance instead of an exception triplet. - `11218 <https://github.com/pytest-dev/pytest/issues/11218>`_: (This entry is meant to assist plugins which access private pytest internals to instantiate ``FixtureRequest`` objects.) :class:`~pytest.FixtureRequest` is now an abstract class which can't be instantiated directly. A new concrete ``TopRequest`` subclass of ``FixtureRequest`` has been added for the ``request`` fixture in test functions, as counterpart to the existing ``SubRequest`` subclass for the ``request`` fixture in fixture functions. - `11315 <https://github.com/pytest-dev/pytest/issues/11315>`_: The :fixture:`pytester` fixture now uses the :fixture:`monkeypatch` fixture to manage the current working directory. If you use ``pytester`` in combination with :func:`monkeypatch.undo() <pytest.MonkeyPatch.undo>`, the CWD might get restored. Use :func:`monkeypatch.context() <pytest.MonkeyPatch.context>` instead. - `11333 <https://github.com/pytest-dev/pytest/issues/11333>`_: Corrected the spelling of ``Config.ArgsSource.INVOCATION_DIR``. The previous spelling ``INCOVATION_DIR`` remains as an alias. - `11638 <https://github.com/pytest-dev/pytest/issues/11638>`_: Fixed the selftests to pass correctly if ``FORCE_COLOR``, ``NO_COLOR`` or ``PY_COLORS`` is set in the calling environment. ``` ### 7.4.4 ``` ========================= Bug Fixes --------- - `11140 <https://github.com/pytest-dev/pytest/issues/11140>`_: Fix non-string constants at the top of file being detected as docstrings on Python>=3.8. - `11572 <https://github.com/pytest-dev/pytest/issues/11572>`_: Handle an edge case where :data:`sys.stderr` and :data:`sys.__stderr__` might already be closed when :ref:`faulthandler` is tearing down. - `11710 <https://github.com/pytest-dev/pytest/issues/11710>`_: Fixed tracebacks from collection errors not getting pruned. - `7966 <https://github.com/pytest-dev/pytest/issues/7966>`_: Removed unhelpful error message from assertion rewrite mechanism when exceptions are raised in ``__iter__`` methods. Now they are treated un-iterable instead. Improved Documentation ---------------------- - `11091 <https://github.com/pytest-dev/pytest/issues/11091>`_: Updated documentation to refer to hyphenated options: replaced ``--junitxml`` with ``--junit-xml`` and ``--collectonly`` with ``--collect-only``. ``` ### 7.4.3 ``` ========================= Bug Fixes --------- - `10447 <https://github.com/pytest-dev/pytest/issues/10447>`_: Markers are now considered in the reverse mro order to ensure base class markers are considered first -- this resolves a regression. - `11239 <https://github.com/pytest-dev/pytest/issues/11239>`_: Fixed ``:=`` in asserts impacting unrelated test cases. - `11439 <https://github.com/pytest-dev/pytest/issues/11439>`_: Handled an edge case where :data:`sys.stderr` might already be closed when :ref:`faulthandler` is tearing down. ``` ### 7.4.2 ``` ========================= Bug Fixes --------- - `11237 <https://github.com/pytest-dev/pytest/issues/11237>`_: Fix doctest collection of `functools.cached_property` objects. - `11306 <https://github.com/pytest-dev/pytest/issues/11306>`_: Fixed bug using ``--importmode=importlib`` which would cause package ``__init__.py`` files to be imported more than once in some cases. - `11367 <https://github.com/pytest-dev/pytest/issues/11367>`_: Fixed bug where `user_properties` where not being saved in the JUnit XML file if a fixture failed during teardown. - `11394 <https://github.com/pytest-dev/pytest/issues/11394>`_: Fixed crash when parsing long command line arguments that might be interpreted as files. Improved Documentation ---------------------- - `11391 <https://github.com/pytest-dev/pytest/issues/11391>`_: Improved disclaimer on pytest plugin reference page to better indicate this is an automated, non-curated listing. ``` ### 7.4.1 ``` ========================= Bug Fixes --------- - `10337 <https://github.com/pytest-dev/pytest/issues/10337>`_: Fixed bug where fake intermediate modules generated by ``--import-mode=importlib`` would not include the child modules as attributes of the parent modules. - `10702 <https://github.com/pytest-dev/pytest/issues/10702>`_: Fixed error assertion handling in :func:`pytest.approx` when ``None`` is an expected or received value when comparing dictionaries. - `10811 <https://github.com/pytest-dev/pytest/issues/10811>`_: Fixed issue when using ``--import-mode=importlib`` together with ``--doctest-modules`` that caused modules to be imported more than once, causing problems with modules that have import side effects. ``` ### 7.4.0 ``` ========================= Features -------- - `10901 <https://github.com/pytest-dev/pytest/issues/10901>`_: Added :func:`ExceptionInfo.from_exception() <pytest.ExceptionInfo.from_exception>`, a simpler way to create an :class:`~pytest.ExceptionInfo` from an exception. This can replace :func:`ExceptionInfo.from_exc_info() <pytest.ExceptionInfo.from_exc_info()>` for most uses. Improvements ------------ - `10872 <https://github.com/pytest-dev/pytest/issues/10872>`_: Update test log report annotation to named tuple and fixed inconsistency in docs for :hook:`pytest_report_teststatus` hook. - `10907 <https://github.com/pytest-dev/pytest/issues/10907>`_: When an exception traceback to be displayed is completely filtered out (by mechanisms such as ``__tracebackhide__``, internal frames, and similar), now only the exception string and the following message are shown: "All traceback entries are hidden. Pass `--full-trace` to see hidden and internal frames.". Previously, the last frame of the traceback was shown, even though it was hidden. - `10940 <https://github.com/pytest-dev/pytest/issues/10940>`_: Improved verbose output (``-vv``) of ``skip`` and ``xfail`` reasons by performing text wrapping while leaving a clear margin for progress output. Added ``TerminalReporter.wrap_write()`` as a helper for that. - `10991 <https://github.com/pytest-dev/pytest/issues/10991>`_: Added handling of ``%f`` directive to print microseconds in log format options, such as ``log-date-format``. - `11005 <https://github.com/pytest-dev/pytest/issues/11005>`_: Added the underlying exception to the cache provider's path creation and write warning messages. - `11013 <https://github.com/pytest-dev/pytest/issues/11013>`_: Added warning when :confval:`testpaths` is set, but paths are not found by glob. In this case, pytest will fall back to searching from the current directory. - `11043 <https://github.com/pytest-dev/pytest/issues/11043>`_: When `--confcutdir` is not specified, and there is no config file present, the conftest cutoff directory (`--confcutdir`) is now set to the :ref:`rootdir <rootdir>`. Previously in such cases, `conftest.py` files would be probed all the way to the root directory of the filesystem. If you are badly affected by this change, consider adding an empty config file to your desired cutoff directory, or explicitly set `--confcutdir`. - `11081 <https://github.com/pytest-dev/pytest/issues/11081>`_: The :confval:`norecursedirs` check is now performed in a :hook:`pytest_ignore_collect` implementation, so plugins can affect it. If after updating to this version you see that your `norecursedirs` setting is not being respected, it means that a conftest or a plugin you use has a bad `pytest_ignore_collect` implementation. Most likely, your hook returns `False` for paths it does not want to ignore, which ends the processing and doesn't allow other plugins, including pytest itself, to ignore the path. The fix is to return `None` instead of `False` for paths your hook doesn't want to ignore. - `8711 <https://github.com/pytest-dev/pytest/issues/8711>`_: :func:`caplog.set_level() <pytest.LogCaptureFixture.set_level>` and :func:`caplog.at_level() <pytest.LogCaptureFixture.at_level>` will temporarily enable the requested ``level`` if ``level`` was disabled globally via ``logging.disable(LEVEL)``. Bug Fixes --------- - `10831 <https://github.com/pytest-dev/pytest/issues/10831>`_: Terminal Reporting: Fixed bug when running in ``--tb=line`` mode where ``pytest.fail(pytrace=False)`` tests report ``None``. - `11068 <https://github.com/pytest-dev/pytest/issues/11068>`_: Fixed the ``--last-failed`` whole-file skipping functionality ("skipped N files") for :ref:`non-python test files <non-python tests>`. - `11104 <https://github.com/pytest-dev/pytest/issues/11104>`_: Fixed a regression in pytest 7.3.2 which caused to :confval:`testpaths` to be considered for loading initial conftests, even when it was not utilized (e.g. when explicit paths were given on the command line). Now the ``testpaths`` are only considered when they are in use. - `1904 <https://github.com/pytest-dev/pytest/issues/1904>`_: Fixed traceback entries hidden with ``__tracebackhide__ = True`` still being shown for chained exceptions (parts after "... the above exception ..." message). - `7781 <https://github.com/pytest-dev/pytest/issues/7781>`_: Fix writing non-encodable text to log file when using ``--debug``. Improved Documentation ---------------------- - `9146 <https://github.com/pytest-dev/pytest/issues/9146>`_: Improved documentation for :func:`caplog.set_level() <pytest.LogCaptureFixture.set_level>`. Trivial/Internal Changes ------------------------ - `11031 <https://github.com/pytest-dev/pytest/issues/11031>`_: Enhanced the CLI flag for ``-c`` to now include ``--config-file`` to make it clear that this flag applies to the usage of a custom config file. ``` ### 7.3.2 ``` ========================= Bug Fixes --------- - `10169 <https://github.com/pytest-dev/pytest/issues/10169>`_: Fix bug where very long option names could cause pytest to break with ``OSError: [Errno 36] File name too long`` on some systems. - `10894 <https://github.com/pytest-dev/pytest/issues/10894>`_: Support for Python 3.12 (beta at the time of writing). - `10987 <https://github.com/pytest-dev/pytest/issues/10987>`_: :confval:`testpaths` is now honored to load root ``conftests``. - `10999 <https://github.com/pytest-dev/pytest/issues/10999>`_: The `monkeypatch` `setitem`/`delitem` type annotations now allow `TypedDict` arguments. - `11028 <https://github.com/pytest-dev/pytest/issues/11028>`_: Fixed bug in assertion rewriting where a variable assigned with the walrus operator could not be used later in a function call. - `11054 <https://github.com/pytest-dev/pytest/issues/11054>`_: Fixed ``--last-failed``'s "(skipped N files)" functionality for files inside of packages (directories with `__init__.py` files). ``` ### 7.3.1 ``` ========================= Improvements ------------ - `10875 <https://github.com/pytest-dev/pytest/issues/10875>`_: Python 3.12 support: fixed ``RuntimeError: TestResult has no addDuration method`` when running ``unittest`` tests. - `10890 <https://github.com/pytest-dev/pytest/issues/10890>`_: Python 3.12 support: fixed ``shutil.rmtree(onerror=...)`` deprecation warning when using :fixture:`tmp_path`. Bug Fixes --------- - `10896 <https://github.com/pytest-dev/pytest/issues/10896>`_: Fixed performance regression related to :fixture:`tmp_path` and the new :confval:`tmp_path_retention_policy` option. - `10903 <https://github.com/pytest-dev/pytest/issues/10903>`_: Fix crash ``INTERNALERROR IndexError: list index out of range`` which happens when displaying an exception where all entries are hidden. This reverts the change "Correctly handle ``__tracebackhide__`` for chained exceptions." introduced in version 7.3.0. ``` ### 7.3.0 ``` ========================= Features -------- - `10525 <https://github.com/pytest-dev/pytest/issues/10525>`_: Test methods decorated with ``classmethod`` can now be discovered as tests, following the same rules as normal methods. This fills the gap that static methods were discoverable as tests but not class methods. - `10755 <https://github.com/pytest-dev/pytest/issues/10755>`_: :confval:`console_output_style` now supports ``progress-even-when-capture-no`` to force the use of the progress output even when capture is disabled. This is useful in large test suites where capture may have significant performance impact. - `7431 <https://github.com/pytest-dev/pytest/issues/7431>`_: ``--log-disable`` CLI option added to disable individual loggers. - `8141 <https://github.com/pytest-dev/pytest/issues/8141>`_: Added :confval:`tmp_path_retention_count` and :confval:`tmp_path_retention_policy` configuration options to control how directories created by the :fixture:`tmp_path` fixture are kept. Improvements ------------ - `10226 <https://github.com/pytest-dev/pytest/issues/10226>`_: If multiple errors are raised in teardown, we now re-raise an ``ExceptionGroup`` of them instead of discarding all but the last. - `10658 <https://github.com/pytest-dev/pytest/issues/10658>`_: Allow ``-p`` arguments to include spaces (eg: ``-p no:logging`` instead of ``-pno:logging``). Mostly useful in the ``addopts`` section of the configuration file. - `10710 <https://github.com/pytest-dev/pytest/issues/10710>`_: Added ``start`` and ``stop`` timestamps to ``TestReport`` objects. - `10727 <https://github.com/pytest-dev/pytest/issues/10727>`_: Split the report header for ``rootdir``, ``config file`` and ``testpaths`` so each has its own line. - `10840 <https://github.com/pytest-dev/pytest/issues/10840>`_: pytest should no longer crash on AST with pathological position attributes, for example testing AST produced by `Hylang <https://github.com/hylang/hy>__`. - `6267 <https://github.com/pytest-dev/pytest/issues/6267>`_: The full output of a test is no longer truncated if the truncation message would be longer than the hidden text. The line number shown has also been fixed. Bug Fixes --------- - `10743 <https://github.com/pytest-dev/pytest/issues/10743>`_: The assertion rewriting mechanism now works correctly when assertion expressions contain the walrus operator. - `10765 <https://github.com/pytest-dev/pytest/issues/10765>`_: Fixed :fixture:`tmp_path` fixture always raising :class:`OSError` on ``emscripten`` platform due to missing :func:`os.getuid`. - `1904 <https://github.com/pytest-dev/pytest/issues/1904>`_: Correctly handle ``__tracebackhide__`` for chained exceptions. NOTE: This change was reverted in version 7.3.1. Improved Documentation ---------------------- - `10782 <https://github.com/pytest-dev/pytest/issues/10782>`_: Fixed the minimal example in :ref:`goodpractices`: ``pip install -e .`` requires a ``version`` entry in ``pyproject.toml`` to run successfully. Trivial/Internal Changes ------------------------ - `10669 <https://github.com/pytest-dev/pytest/issues/10669>`_: pytest no longer directly depends on the `attrs <https://www.attrs.org/en/stable/>`__ package. While we at pytest all love the package dearly and would like to thank the ``attrs`` team for many years of cooperation and support, it makes sense for ``pytest`` to have as little external dependencies as possible, as this helps downstream projects. With that in mind, we have replaced the pytest's limited internal usage to use the standard library's ``dataclasses`` instead. Nice diffs for ``attrs`` classes are still supported though. ```
Links - PyPI: https://pypi.org/project/pytest - Changelog: https://data.safetycli.com/changelogs/pytest/

Update pytest-asyncio from 0.20.3 to 0.23.6.

Changelog ### 0.23.6 ``` - Fix compatibility with pytest 8.2 [800](https://github.com/pytest-dev/pytest-asyncio/pull/800) Known issues As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see [706](https://github.com/pytest-dev/pytest-asyncio/issues/706)). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved. ``` ### 0.23.5 ``` - Declare compatibility with pytest 8 [737](https://github.com/pytest-dev/pytest-asyncio/issues/737) - Fix typing errors with recent versions of mypy [769](https://github.com/pytest-dev/pytest-asyncio/issues/769) Known issues As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see [706](https://github.com/pytest-dev/pytest-asyncio/issues/706)). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved. ``` ### 0.23.4 ``` - pytest-asyncio no longer imports additional, unrelated packages during test collection [729](https://github.com/pytest-dev/pytest-asyncio/issues/729) Known issues As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see [706](https://github.com/pytest-dev/pytest-asyncio/issues/706)). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved. ``` ### 0.23.3 ``` - Fixes a bug that caused event loops to be closed prematurely when using async generator fixtures with class scope or wider in a function-scoped test [708](https://github.com/pytest-dev/pytest-asyncio/issues/708) - Fixes a bug that caused an internal pytest error when using unittest.SkipTest in a module [711](https://github.com/pytest-dev/pytest-asyncio/issues/711) ``` ### 0.23.2 ``` - Fixes a bug that caused an internal pytest error when collecting .txt files [703](https://github.com/pytest-dev/pytest-asyncio/issues/703) ``` ### 0.23.1 ``` - Fixes a bug that caused an internal pytest error when using module-level skips [701](https://github.com/pytest-dev/pytest-asyncio/issues/701) ``` ### 0.23.0 ``` This release is backwards-compatible with v0.21. Changes are non-breaking, unless you upgrade from v0.22. * BREAKING: The _asyncio_event_loop_ mark has been removed. Event loops with class, module, package, and session scopes can be requested via the _scope_ keyword argument to the _asyncio_ mark. * Introduces the _event_loop_policy_ fixture which allows testing with non-default or multiple event loops [662](https://github.com/pytest-dev/pytest-asyncio/pull/662) * Removes pytest-trio from the test dependencies [620](https://github.com/pytest-dev/pytest-asyncio/pull/620) ``` ### 0.22.0 ``` * Class-scoped and module-scoped event loops can be requested via the _asyncio_event_loop_ mark. [620](https://github.com/pytest-dev/pytest-asyncio/pull/620) * Deprecate redefinition of the _event_loop_ fixture. [587](https://github.com/pytest-dev/pytest-asyncio/issues/531) Users requiring a class-scoped or module-scoped asyncio event loop for their tests should mark the corresponding class or module with _asyncio_event_loop_. * Test items based on asynchronous generators always exit with _xfail_ status and emit a warning during the collection phase. This behavior is consistent with synchronous yield tests. [642](https://github.com/pytest-dev/pytest-asyncio/issues/642) * Remove support for Python 3.7 * Declare support for Python 3.12 ``` ### 0.21.1 ``` * Output a proper error message when an invalid `asyncio_mode` is selected. * Extend warning message about unclosed event loops with additional possible cause. 531 * Previously, some tests reported "skipped" or "xfailed" as a result. Now all tests report a "success" result. ``` ### 0.21.0 ``` * Drop compatibility with pytest 6.1. Pytest-asyncio now depends on pytest 7.0 or newer. * pytest-asyncio cleans up any stale event loops when setting up and tearing down the event_loop fixture. This behavior has been deprecated and pytest-asyncio emits a DeprecationWarning when tearing down the event_loop fixture and current event loop has not been closed. ```
Links - PyPI: https://pypi.org/project/pytest-asyncio - Changelog: https://data.safetycli.com/changelogs/pytest-asyncio/ - Repo: https://github.com/pytest-dev/pytest-asyncio

Update markdown from 3.4.1 to 3.6.

Changelog ### 3.5.2 ``` Fixed * Fix type annotations for `convertFile` - it accepts only bytes-based buffers. Also remove legacy checks from Python 2 (1400) * Remove legacy import needed only in Python 2 (1403) * Fix typo that left the attribute `AdmonitionProcessor.content_indent` unset (1404) * Fix edge-case crash in `InlineProcessor` with `AtomicString` (1406). * Fix edge-case crash in `codehilite` with an empty `code` tag (1405). * Improve and expand type annotations in the code base (1401). * Fix handling of bogus comments (1425). ``` ### 3.5.1 ``` Fixed * Fix a performance problem with HTML extraction where large HTML input could trigger quadratic line counting behavior (1392). * Improve and expand type annotations in the code base (1394). ```
Links - PyPI: https://pypi.org/project/markdown - Changelog: https://data.safetycli.com/changelogs/markdown/

Update pillow from 9.4.0 to 10.3.0.

Changelog ### 10.3.0 ``` https://pillow.readthedocs.io/en/stable/releasenotes/10.3.0.html Changes - CVE-2024-28219: Use strncpy to avoid buffer overflow 7928 [hugovk] - Use `functools.lru_cache` for `hopper()` 7912 [hugovk] - Raise ValueError if seeking to greater than offset-sized integer in TIFF 7883 [radarhere] - Improve speed of loading QOI images 7925 [radarhere] - Added RGB to I;16N conversion 7920 [radarhere] - Add --report argument to __main__.py to omit supported formats 7818 [nulano] - Added RGB to I;16, I;16L and I;16B conversion 7918 [radarhere] - Fix editable installation with custom build backend and configuration options 7658 [nulano] - Fix putdata() for I;16N on big-endian 7209 [Yay295] - Determine MPO size from markers, not EXIF data 7884 [radarhere] - Improved conversion from RGB to RGBa, LA and La 7888 [radarhere] - Support FITS images with GZIP_1 compression 7894 [radarhere] - Use I;16 mode for 9-bit JPEG 2000 images 7900 [scaramallion] - Raise ValueError if kmeans is negative 7891 [radarhere] - Remove TIFF tag OSUBFILETYPE when saving using libtiff 7893 [radarhere] - Raise ValueError for negative values when loading P1-P3 PPM images 7882 [radarhere] - Added reading of JPEG2000 palettes 7870 [radarhere] - Added alpha_quality argument when saving WebP images 7872 [radarhere] - Fixed joined corners for ImageDraw rounded_rectangle() non-integer dimensions 7881 [radarhere] - Removed Python and NumPy pinning on Cygwin 7880 [radarhere] - Update UnidentifiedImageError and __version__ imports 7644 [radarhere] - Stop reading EPS image at EOF marker 7753 [radarhere] - PSD layer co-ordinates may be negative 7706 [radarhere] - Use subprocess with CREATE_NO_WINDOW flag in ImageShow WindowsViewer 7791 [radarhere] - When saving GIF frame that restores to background color, do not fill identical pixels 7788 [radarhere] - Fixed reading PNG iCCP compression method 7823 [radarhere] - Allow writing IFDRational to UNDEFINED tag 7840 [radarhere] - Fix logged tag name when loading Exif data 7842 [radarhere] - Use maximum frame size in IHDR chunk when saving APNG images 7821 [radarhere] - Prevent opening P TGA images without a palette 7797 [radarhere] - Use palette when loading ICO images 7798 [radarhere] - Use consistent arguments for load_read and load_seek 7713 [radarhere] - Turn off nullability warnings for macOS SDK 7827 [radarhere] - Fix shift-sign issue in Convert.c 7838 [r-barnes] - winbuild: Refactor dependency versions into constants 7843 [hugovk] - Build macOS arm64 wheels natively 7852 [radarhere] - Fixed typo 7855 [radarhere] - Open 16-bit grayscale PNGs as I;16 7849 [radarhere] - Handle truncated chunks at the end of PNG images 7709 [lajiyuan] - Match mask size to pasted image size in GifImagePlugin 7779 [radarhere] - Changed SupportsGetMesh protocol to be public 7841 [radarhere] - Release GIL while calling `WebPAnimDecoderGetNext` 7782 [evanmiller] - Fixed reading FLI/FLC images with a prefix chunk 7804 [twolife] - Updated package name for Tidelift 7810 [radarhere] - Removed unused code 7744 [radarhere] - Lint fix 7783 [radarhere] - Update wl-paste handling and return None for some errors in grabclipboard() on Linux 7745 [nik012003] - Fixed libXau error in wheels for macOS 10.10 7764 [radarhere] - Changed name of first _Tile parameter 7772 [radarhere] - Remove execute bit from `setup.py` 7760 [hugovk] - Changed ImageMath.ops to be static 7721 [radarhere] - Fix APNG info after seeking backwards more than twice 7701 [esoma] - Removed PPM loop to read header tokens 7698 [radarhere] - Added PerspectiveTransform 7699 [radarhere] - Add support for reading and writing grayscale PFM images 7696 [nulano] - Add LCMS2 flags to ImageCms 7676 [nulano] - Rename x64 to AMD64 in winbuild 7693 [nulano] - Build QEMU-emulated Linux aarch64 wheels on GitHub Actions instead of Travis CI 7690 [hugovk] - Simplify FreeTypeFont.getmask2() 7645 [nulano] - Updated Linux and macOS wheels matrix variable name 7691 [radarhere] - Skip PyPy3.8 Windows wheel 7682 [radarhere] Deprecations - Deprecate eval(), replacing it with lambda_eval() and unsafe_eval() 7927 [hugovk] - Deprecate ImageCms constants and versions() function 7702 [nulano] Documentation - Add type hints to release notes 7923 [hugovk] - Corrected exiv2.org links 7856 [radarhere] - Removed references to the "current version" 7905 [radarhere] - Added release notes for 7872, 7882 and 7891 7904 [radarhere] - Clean up authors and contributors 7895 [aclark4life] - Update release notes 7885 [hugovk] - Backfill release notes with security fix details 7877 [aclark4life] - Describe difference between font size and bbox 7806 [radarhere] - Decoders and encoders subclass PyDecoder and PyEncoder 7801 [radarhere] - Update CI targets on GitHub Actions 7862 [hugovk] - Update "What about PIL?" section 7861 [aclark4life] - Update installation docs 7858 [hugovk] - Move installation.rst to installation/*.rst 7832 [aclark4life] - Removed references to Twitter 7836 [radarhere] - Consistently place versionremoved under heading 7829 [radarhere] - Remove outdated installation warnings 7814 [hugovk] - PyPI project page URL is now lowercase 7703 [nulano] - Use "non-zero" consistently 7695 [radarhere] - Improve ImageTransform documentation 7684 [nulano] - If ImageGrab.grab() bbox is omitted, screenshot is taken at 2x on Retina screens 7688 [radarhere] - Updated macOS tested Pillow versions 7689 [radarhere] - Update Windows 11 tested versions 7685 [nulano] - ImageGrab.grab() bbox on macOS is not 2x on retina screens 7678 [radarhere] - Package name is now lowercase in wheel filenames 7681 [radarhere] Type hints - Add type hints for ImageCms 7913 [nulano] - Add type hints to `Image.py` 7924 [hugovk] - Add type hints to release notes 7923 [hugovk] - Added `py.typed` and `Typing :: Typed` to support type checking 7822 [radarhere] - Added remaining type hints to Tests/test_image_*.py 7793 [radarhere] - Added type hints for ImageShow 7712 [radarhere] - Added type hints to additional tests 7754 [radarhere] - Added type hints to additional tests 7755 [radarhere] - Added type hints to additional tests 7769 [radarhere] - Added type hints to additional tests 7784 [radarhere] - Added type hints to additional tests 7794 [radarhere] - Added type hints to additional tests 7807 [radarhere] - Added type hints to additional tests 7816 [radarhere] - Added type hints to additional tests 7846 [radarhere] - Added type hints to FitsImagePlugin 7714 [radarhere] - Added type hints to GdImageFile 7727 [radarhere] - Added type hints to ImageMath 7707 [radarhere] - Added type hints to ImageMorph 7708 [radarhere] - Added type hints to ImageOps 7786 [radarhere] - Added type hints to ImtImagePlugin 7720 [radarhere] - Added type hints to MpegImagePlugin 7728 [radarhere] - Added type hints to MspImagePlugin 7719 [radarhere] - Added type hints to OSS Fuzz scripts 7731 [radarhere] - Added type hints to PpmImagePlugin 7726 [radarhere] - Added type hints to seven plugins 7716 [radarhere] - Added type hints to SgiImagePlugin 7724 [radarhere] - Added type hints to Tests/check_*.py 7732 [radarhere] - Added type hints to Tests/conftest.py 7740 [radarhere] - Added type hints to Tests/helper.py 7733 [radarhere] - Added type hints to Tests/test_font_*.py 7743 [radarhere] - Added type hints to TgaImagePlugin 7725 [radarhere] - Autotype tests 7756 [hugovk] - Decoders and encoders subclass PyDecoder and PyEncoder 7801 [radarhere] - Removed mypy excludes 7808 [radarhere] - Removed mypy excludes, except for olefile-related files 7790 [radarhere] - Replace `io.BytesIO` in type hints 7750 [hugovk] - Type hints: Add PYI (flake8-pyi) to Ruff and fix errors 7897 [hugovk] - Use IO[bytes] in type hints 7795 [radarhere] Dependencies - [pre-commit.ci] pre-commit autoupdate and fix deprecations 7780 [pre-commit-ci] - Install mypy from requirements file 7813 [hugovk] - Pin codecov/codecov-action to v3.1.5 7776 [hugovk] - Update actions/cache action to v4 7735 [renovate] - Update dependency cibuildwheel to v2.16.4 7758 [renovate] - Update dependency cibuildwheel to v2.16.5 7767 [renovate] - Update dependency cibuildwheel to v2.17.0 7869 [renovate] - Update dependency mypy to v1.8.0 7851 [renovate] - Update dependency mypy to v1.9.0 7866 [renovate] - Update github-actions to v4 7770 [renovate] - Update release-drafter/release-drafter action to v6 7774 [renovate] - Updated Ghostscript to 10.3.0 7887 [radarhere] - Updated giflib on macOS to 5.2.2 7815 [radarhere] - Updated harfbuzz to 8.3.1 7886 [radarhere] - Updated harfbuzz to 8.4.0 7917 [radarhere] - Updated libimagequant to 4.3.0 7749 [radarhere] - Updated libjpeg-turbo to 3.0.2 7752 [radarhere] - Updated libpng to 1.6.43 7768 [radarhere] - Updated libxcb to 1.16.1 7853 [radarhere] - Updated openjpeg to 2.5.2 7837 [radarhere] - Updated xorgproto to 2024.1 7907 [radarhere] - Updated zlib to 1.3.1 7746 [radarhere] - Testing - Use setup_module() to open images so they aren't opened if skipped 7911 [Yay295] - Skip AppVeyor builds for irrelevant files 7909 [hugovk] - Revert "Pin Python 3.13 on Windows to a3" 7878 [radarhere] - Restored testing of non-TrueType default font 7748 [radarhere] - Parametrize test_seek_mode functions 7847 [Yay295] - Do not use packaged MinGW pip 7844 [radarhere] - Parametrize test_p_from_rgb_rgba() 7835 [Yay295] - Require coverage.py 7.4.2+ for `COVERAGE_CORE: sysmon` 7825 [hugovk] - Set `COVERAGE_CORE: sysmon` for faster tests on 3.12+ 7820 [hugovk] - Build docs for Python changes 7819 [nulano] - Install mypy from requirements file 7813 [hugovk] - Pin Python 3.13 on Windows to a3 7805 [radarhere] - Removed platform argument from setup-cygwin action 7775 [radarhere] - Pin to Python 3.9.16-1 7762 [radarhere] - Test on macOS M1 where available 7766 [hugovk] - CI: Cache libimagequant on Linux builds 7741 [hugovk] - Do not support using test-image-results to upload images after test failures 7739 [radarhere] - Sort imports in `Tests/` 7736 [hugovk] - Skip non-wheel CI runs for tags: Windows 7692 [hugovk] ``` ### 10.2.0 ``` https://pillow.readthedocs.io/en/stable/releasenotes/10.2.0.html Changes - Add `keep_rgb` option when saving JPEG to prevent conversion of RGB colorspace 7553 [bgilbert] - Trim negative glyph offsets in ImageFont.getmask() 7672 [nulano] - Removed unnecessary "pragma: no cover" 7668 [radarhere] - Trim glyph size in ImageFont.getmask() 7669 [radarhere] - Fix loading IPTC images and update test 7667 [nulano] - Allow uncompressed TIFF images to be saved in chunks 7650 [radarhere] - Concatenate multiple JPEG EXIF markers 7496 [radarhere] - Changed IPTC tile tuple to match other plugins 7661 [radarhere] - Do not assign new fp attribute when exiting context manager 7566 [radarhere] - Support arbitrary masks for uncompressed RGB DDS images 7589 [radarhere] - Support setting ROWSPERSTRIP tag 7654 [radarhere] - Apply ImageFont.MAX_STRING_LENGTH to ImageFont.getmask() 7662 [radarhere] - Optimise `ImageColor` using `functools.lru_cache` 7657 [hugovk] - Restricted environment keys for ImageMath.eval() 7655 [radarhere] - Optimise `ImageMode.getmode` using `functools.lru_cache` 7641 [hugovk] - Added trusted PyPI publishing 7616 [radarhere] - Compile FriBiDi for Windows ARM64 7629 [nulano] - Fix incorrect color blending for overlapping glyphs 7497 [ZachNagengast] - Add .git-blame-ignore-revs file 7528 [akx] - Attempt memory mapping when tile args is a string 7565 [radarhere] - Fill identical pixels with transparency in subsequent frames when saving GIF 7568 [radarhere] - Removed unnecessary string length check 7560 [radarhere] - Determine mask mode in Python instead of C 7548 [radarhere] - Corrected duration when combining multiple GIF frames into single frame 7521 [radarhere] - Handle disposing GIF background from outside palette 7515 [radarhere] - Seek past the data when skipping a PSD layer 7483 [radarhere] - ImageMath: Inline `isinstance` check 7623 [hugovk] - Update actions/upload-artifact action to v4 7619 [radarhere] - Import plugins relative to the module 7576 [deliangyang] - Translate encoder error codes to strings; deprecate `ImageFile.raise_oserror()` 7609 [bgilbert] - Updated readthedocs to latest version of Python 7611 [radarhere] - Support reading BC4U and DX10 BC1 images 6486 [REDxEYE] - Optimize ImageStat.Stat.extrema 7593 [florath] - Handle pathlib.Path in FreeTypeFont 7578 [radarhere] - Use list comprehensions to create transformed lists 7597 [hugovk] - Added support for reading DX10 BC4 DDS images 7603 [sambvfx] - Optimized ImageStat.Stat.count 7599 [florath] - Moved error from truetype() to FreeTypeFont 7587 [radarhere] - Correct PDF palette size when saving 7555 [radarhere] - Fixed closing file pointer with olefile 0.47 7594 [radarhere] - ruff: Minor optimizations of list comprehensions, x in set, etc. 7524 [cclauss] - Build Windows wheels using cibuildwheel 7580 [nulano] - Raise ValueError when TrueType font size is zero or less 7584 [akx] - Install cibuildwheel from requirements file 7581 [hugovk] - List optional dependencies in pyproject (apart from docs and tests) 7563 [radarhere] - Use cibuildwheel 7552 [radarhere] - "optimize" default when saving GIF images 7570 [radarhere] - If absent, do not try to close fp when closing image 7557 [RaphaelVRossi] - Windows arm64 dependency cross-compilation fixes 7559 [nulano] - Allow configuring JPEG restart marker interval on save 7488 [bgilbert] - Decrement reference count for PyObject 7549 [radarhere] - Release automation: create sdist on CI 7544 [hugovk
pyup-bot commented 5 months ago

Closing this in favor of #404