Skip to content

[deps]: Lock file maintenance poetry #82

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[deps]: Lock file maintenance poetry #82

wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 6, 2025 •
edited
Loading

This PR contains the following updates:

Package Type Update Change Age Confidence
lockFileMaintenance All locks refreshed
docformatter dev patch 1.7.5 -> 1.7.7 age confidence
flake8 (changelog) dev minor 7.1.1 -> 7.3.0 age confidence
marshmallow (changelog) dependencies minor 3.23.2 -> 3.26.1 age confidence
mypy (changelog) dev minor 1.14.1 -> 1.18.2 age confidence
pre-commit dev minor 4.0.1 -> 4.4.0 age confidence
pytest (changelog) test minor 8.3.4 -> 8.4.2 age confidence
pytest-httpserver test patch 1.1.0 -> 1.1.3 age confidence
pytest-mock (changelog) test minor 3.14.0 -> 3.15.1 age confidence
python-dotenv dev minor 1.0.1 -> 1.2.1 age confidence
requests (source, changelog) dependencies patch 2.32.4 -> 2.32.5 age confidence
types-requests (changelog) dev patch 2.32.0.20241016 -> 2.32.4.20250913 age confidence

🔧 This Pull Request updates lock files to use the latest dependency versions.

Release Notes

PyCQA/docformatter (docformatter)

v1.7.7

Compare Source

Full Changelog

Merged pull requests:

v1.7.6

Compare Source

Full Changelog

Merged pull requests:

pycqa/flake8 (flake8)

v7.3.0

Compare Source

v7.2.0

Compare Source

v7.1.2

Compare Source

marshmallow-code/marshmallow (marshmallow)

v3.26.1

Compare Source

v3.26.0

Compare Source

v3.25.1

Compare Source

v3.25.0

Compare Source

v3.24.2

Compare Source

v3.24.1

Compare Source

v3.24.0

Compare Source

v3.23.3

Compare Source

python/mypy (mypy)

v1.18.2

Compare Source

  • Fix crash on recursive alias (Ivan Levkivskyi, PR 19845)
  • Add additional guidance for stubtest errors when runtime is object.__init__ (Stephen Morton, PR 19733)
  • Fix handling of None values in f-string expressions in mypyc (BobTheBuidler, PR 19846)

v1.18.1

Compare Source

We’ve just uploaded mypy 1.18.1 to the Python Package Index (PyPI).
Mypy is a static type checker for Python. This release includes new features, performance
improvements and bug fixes. You can install it as follows:

python3 -m pip install -U mypy

You can read the full documentation for this release on Read the Docs.

Mypy Performance Improvements

Mypy 1.18.1 includes numerous performance improvements, resulting in about 40% speedup
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, 19769, 19770)
  • Optimize fixed-format deserialization (Ivan Levkivskyi, PR 19765)
  • Use macros to optimize fixed-format deserialization (Ivan Levkivskyi, PR 19757)
  • Two additional micro‑optimizations (Ivan Levkivskyi, PR 19627)
  • Another set of micro‑optimizations (Ivan Levkivskyi, PR 19633)
  • Cache common types (Ivan Levkivskyi, PR 19621)
  • Skip more method bodies in third‑party libraries for speed (Ivan Levkivskyi, PR 19586)
  • Simplify the representation of callable types (Ivan Levkivskyi, PR 19580)
  • Add cache for types of some expressions (Ivan Levkivskyi, PR 19505)
  • Use cache for dictionary expressions (Ivan Levkivskyi, PR 19536)
  • Use cache for binary operations (Ivan Levkivskyi, PR 19523)
  • Cache types of type objects (Ivan Levkivskyi, PR 19514)
  • Avoid duplicate work when checking boolean operations (Ivan Levkivskyi, PR 19515)
  • Optimize generic inference passes (Ivan Levkivskyi, PR 19501)
  • Speed up the default plugin (Jukka Lehtosalo, PRs 19385 and 19462)
  • Remove nested imports from the default plugin (Ivan Levkivskyi, PR 19388)
  • Micro‑optimize type expansion (Jukka Lehtosalo, PR 19461)
  • Micro‑optimize type indirection (Jukka Lehtosalo, PR 19460)
  • Micro‑optimize the plugin framework (Jukka Lehtosalo, PR 19464)
  • Avoid temporary set creation in subtype checking (Jukka Lehtosalo, PR 19463)
  • Subtype checking micro‑optimization (Jukka Lehtosalo, PR 19384)
  • Return early where possible in subtype check (Stanislav Terliakov, PR 19400)
  • Deduplicate some types before joining (Stanislav Terliakov, PR 19409)
  • Speed up type checking by caching argument inference context (Jukka Lehtosalo, PR 19323)
  • Optimize binding method self argument type and deprecation checks (Ivan Levkivskyi, PR 19556)
  • Keep trivial instance types/aliases during expansion (Ivan Levkivskyi, PR 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'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, 19735, 19750, 19681, 19752, 19815).

Flexible Variable Definitions: Update

Mypy 1.16.0 introduced --allow-redefinition-new, which allows redefining variables
with different types, and inferring union types for variables from multiple assignments.
The feature is now documented in the --help output, but the feature is still experimental.

We are planning to enable this by default in mypy 2.0, and we will also deprecate the
older --allow-redefinition flag. Since the new behavior differs significantly from
the older flag, we encourage users of --allow-redefinition to experiment with
--allow-redefinition-new and create a GitHub issue if the new functionality doesn't
support some important use cases.

This feature was contributed by Jukka Lehtosalo.

Inferred Type for Bare ClassVar

A ClassVar without an explicit type annotation now causes the type of the variable
to be inferred from the initializer:

from typing import ClassVar

class Item:

### Type of 'next_id' is now 'int' (it was 'Any')
    next_id: ClassVar = 1

    ...

This feature was contributed by Ivan Levkivskyi (PR 19573).

Disjoint Base Classes (@​disjoint_base, PEP 800)

Mypy now understands disjoint bases (PEP 800): it recognizes the @disjoint_base
decorator, and rejects class definitions that combine mutually incompatible base classes,
and takes advantage of the fact that such classes cannot exist in reachability and
narrowing logic.

This class definition will now generate an error:



v1.17.1


Compare Source


    

  • Retain None as constraints bottom if no bottoms were provided (Stanislav Terliakov, PR 19485)
    • 

  • Fix "ignored exception in hasattr" in dmypy (Stanislav Terliakov, PR 19428)
    • 

  • Prevent a crash when InitVar is redefined with a method in a subclass (Stanislav Terliakov, PR 19453)
    • 



v1.17.0


Compare Source


v1.16.1


Compare Source


v1.16.0


Compare Source


v1.15.0


Compare Source





pre-commit/pre-commit (pre-commit)

v4.4.0


Compare Source


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


Features



Fixes



v4.3.0


Compare Source


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


Features



v4.2.0


Compare Source


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


Features


    

  • For language: python first attempt a versioned python executable for
    
the default language version before consulting a potentially unversioned
    
sys.executable.


    • 



Fixes



v4.1.0


Compare Source


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


Features



Fixes






pytest-dev/pytest (pytest)

v8.4.2


Compare Source


pytest 8.4.2 (2025-09-03)


Bug fixes


    

  • 

    #​13478: Fixed a crash when using console_output_style{.interpreted-text role="confval"} with times and a module is skipped.
    

    • 

  • 

    #​13530: Fixed a crash when using pytest.approx{.interpreted-text role="func"} and decimal.Decimal{.interpreted-text role="class"} instances with the decimal.FloatOperation{.interpreted-text role="class"} trap set.
    

    • 

  • 

    #​13549: 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: Added missing [int]{.title-ref} and [float]{.title-ref} variants to the [Literal]{.title-ref} type annotation of the [type]{.title-ref} parameter in pytest.Parser.addini{.interpreted-text role="meth"}.
    

    • 

  • 

    #​13563: pytest.approx{.interpreted-text role="func"} now only imports numpy if NumPy is already in sys.modules. This fixes unconditional import behavior introduced in [8.4.0]{.title-ref}.
    

    • 



Improved documentation


    

  • #​13577: Clarify that pytest_generate_tests is discovered in test modules/classes; other hooks must be in conftest.py or plugins.
    • 



Contributor-facing changes


    

  • #​13480: Self-testing: fixed a few test failures when run with -Wdefault or a similar override.
    • 

  • #​13547: Self-testing: corrected expected message for test_doctest_unexpected_exception in Python 3.14.
    • 

  • #​13684: Make pytest's own testsuite insensitive to the presence of the CI environment variable -- by ogrisel{.interpreted-text role="user"}.
    • 



v8.4.1


Compare Source


pytest 8.4.1 (2025-06-17)


Bug fixes


    

  • 

    #​13461: Corrected _pytest.terminal.TerminalReporter.isatty to support
    
being called as a method. Before it was just a boolean which could
    
break correct code when using -o log_cli=true).
    

    • 

  • 

    #​13477: Reintroduced pytest.PytestReturnNotNoneWarning{.interpreted-text role="class"} which was removed by accident in pytest [8.4]{.title-ref}.
    

    This warning is raised when a test functions returns a value other than None, which is often a mistake made by beginners.
    

    See return-not-none{.interpreted-text role="ref"} for more information.
    

    • 

  • 

    #​13497: Fixed compatibility with Twisted 25+.
    

    • 



Improved documentation


    

  • #​13492: Fixed outdated warning about faulthandler not working on Windows.
    • 



v8.4.0


Compare Source


pytest 8.4.0 (2025-06-02)


Removals and backward incompatible breaking changes


    

  • 

    #​11372: Async tests will now fail, instead of warning+skipping, if you don't have any suitable plugin installed.
    

    • 

  • 

    #​12346: Tests will now fail, instead of raising a warning, if they return any value other than None.
    

    • 

  • 

    #​12874: We dropped support for Python 3.8 following its end of life (2024-10-07).
    

    • 

  • 

    #​12960: Test functions containing a yield now cause an explicit error. They have not been run since pytest 4.0, and were previously marked as an expected failure and deprecation warning.
    

    See the docs <yield tests deprecated>{.interpreted-text role="ref"} for more information.
    

    • 



Deprecations (removal in next major release)


    

  • #​10839: Requesting an asynchronous fixture without a [pytest_fixture_setup]{.title-ref} hook that resolves it will now give a DeprecationWarning. This most commonly happens if a sync test requests an async fixture. This should have no effect on a majority of users with async tests or fixtures using async pytest plugins, but may affect non-standard hook setups or autouse=True. For guidance on how to work around this warning see sync-test-async-fixture{.interpreted-text role="ref"}.
    • 



New features


    

  • 

    #​11538: Added pytest.RaisesGroup{.interpreted-text role="class"} as an equivalent to pytest.raises{.interpreted-text role="func"} for expecting ExceptionGroup{.interpreted-text role="exc"}. Also adds pytest.RaisesExc{.interpreted-text role="class"} which is now the logic behind pytest.raises{.interpreted-text role="func"} and used as parameter to pytest.RaisesGroup{.interpreted-text role="class"}. RaisesGroup includes the ability to specify multiple different expected exceptions, the structure of nested exception groups, and flags for emulating except* <except_star>{.interpreted-text role="ref"}. See assert-matching-exception-groups{.interpreted-text role="ref"} and docstrings for more information.
    

    • 

  • 

    #​12081: Added capteesys{.interpreted-text role="fixture"} to capture AND pass output to next handler set by --capture=.
    

    • 

  • 

    #​12504: pytest.mark.xfail{.interpreted-text role="func"} now accepts pytest.RaisesGroup{.interpreted-text role="class"} for the raises parameter when you expect an exception group. You can also pass a pytest.RaisesExc{.interpreted-text role="class"} if you e.g. want to make use of the check parameter.
    

    • 

  • 

    #​12713: New [--force-short-summary]{.title-ref} option to force condensed summary output regardless of verbosity level.
    

    This lets users still see condensed summary output of failures for quick reference in log files from job outputs, being especially useful if non-condensed output is very verbose.
    

    • 

  • 

    #​12749: pytest traditionally collects classes/functions in the test module namespace even if they are imported from another file.
    

    For example:
    

    

    • 



contents of src/domain.py


class Testament: ...



contents of tests/test_testament.py


from domain import Testament

def test_testament(): ...
```

In this scenario with the default options, pytest will collect the class [Testament]{.title-ref} from [tests/test_testament.py]{.title-ref} because it starts with [Test]{.title-ref}, even though in this case it is a production class being imported in the test module namespace.

This behavior can now be prevented by setting the new `collect_imported_tests`{.interpreted-text role="confval"} configuration option to `false`, which will make pytest collect classes/functions from test files **only** if they are defined in that file.

\-- by `FreerGit`{.interpreted-text role="user"}



    

  • 

    #​12765: Thresholds to trigger snippet truncation can now be set with truncation_limit_lines{.interpreted-text role="confval"} and truncation_limit_chars{.interpreted-text role="confval"}.
    

    See truncation-params{.interpreted-text role="ref"} for more information.
    

    • 

  • 

    #​13125: console_output_style{.interpreted-text role="confval"} now supports times to show execution time of each test.
    

    • 

  • 

    #​13192: pytest.raises{.interpreted-text role="func"} will now raise a warning when passing an empty string to match, as this will match against any value. Use match="^$" if you want to check that an exception has no message.
    

    • 

  • 

    #​13192: pytest.raises{.interpreted-text role="func"} will now print a helpful string diff if matching fails and the match parameter has ^ and $ and is otherwise escaped.
    

    • 

  • 

    #​13192: You can now pass with pytest.raises(check=fn): <pytest.raises>{.interpreted-text role="func"}, where fn is a function which takes a raised exception and returns a boolean. The raises fails if no exception was raised (as usual), passes if an exception is raised and fn returns True (as well as match and the type matching, if specified, which are checked before), and propagates the exception if fn returns False (which likely also fails the test).
    

    • 

  • 

    #​13228: hidden-param{.interpreted-text role="ref"} can now be used in id of pytest.param{.interpreted-text role="func"} or in
    
ids of Metafunc.parametrize <pytest.Metafunc.parametrize>{.interpreted-text role="py:func"}.
    
It hides the parameter set from the test name.
    

    • 

  • 

    #​13253: New flag: --disable-plugin-autoload <disable_plugin_autoload>{.interpreted-text role="ref"} which works as an alternative to PYTEST_DISABLE_PLUGIN_AUTOLOAD{.interpreted-text role="envvar"} when setting environment variables is inconvenient; and allows setting it in config files with addopts{.interpreted-text role="confval"}.
    

    • 



Improvements in existing functionality


    

  • 

    #​10224: pytest's short and long traceback styles (how-to-modifying-python-tb-printing{.interpreted-text role="ref"})
    
now have partial 657{.interpreted-text role="pep"} support and will show specific code segments in the
    
traceback.
    

    ================================= FAILURES =================================
_______________________ test_gets_correct_tracebacks _______________________

test_tracebacks.py:12: in test_gets_correct_tracebacks
    assert manhattan_distance(p1, p2) == 1
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
test_tracebacks.py:6: in manhattan_distance
    return abs(point_1.x - point_2.x) + abs(point_1.y - point_2.y)
                           ^^^^^^^^^
E   AttributeError: 'NoneType' object has no attribute 'x'

    

    -- by ammaraskar{.interpreted-text role="user"}
    

    • 

  • 

    #​11118: Now pythonpath{.interpreted-text role="confval"} configures [$PYTHONPATH]{.title-ref} earlier than before during the initialization process, which now also affects plugins loaded via the [-p]{.title-ref} command-line option.
    

    -- by millerdev{.interpreted-text role="user"}
    

    • 

  • 

    #​11381: The type parameter of the parser.addini method now accepts ["int"]{.title-ref} and "float" parameters, facilitating the parsing of configuration values in the configuration file.
    

    Example:
    

    def pytest_addoption(parser):
    parser.addini("int_value", type="int", default=2, help="my int value")
    parser.addini("float_value", type="float", default=4.2, help="my float value")
    

    The [pytest.ini]{.title-ref} file:
    

    [pytest]
int_value = 3
float_value = 5.4
    

    • 

  • 

    #​11525: Fixtures are now clearly represented in the output as a "fixture object", not as a normal function as before, making it easy for beginners to catch mistakes such as referencing a fixture declared in the same module but not requested in the test function.
    

    -- by the-compiler{.interpreted-text role="user"} and glyphack{.interpreted-text role="user"}
    

    • 

  • 

    #​12426: A warning is now issued when pytest.mark.usefixtures ref{.interpreted-text role="ref"} is used without specifying any fixtures. Previously, empty usefixtures markers were silently ignored.
    

    • 

  • 

    #​12707: Exception chains can be navigated when dropped into Pdb in Python 3.13+.
    

    • 

  • 

    #​12736: Added a new attribute [name]{.title-ref} with the fixed value ["pytest tests"]{.title-ref} to the root tag [testsuites]{.title-ref} of the junit-xml generated by pytest.
    

    This attribute is part of many junit-xml specifications and is even part of the [junit-10.xsd]{.title-ref} specification that pytest's implementation is based on.
    

    • 

  • 

    #​12943: If a test fails with an exceptiongroup with a single exception, the contained exception will now be displayed in the short test summary info.
    

    • 

  • 

    #​12958: A number of unraisable <unraisable>{.interpreted-text role="ref"} enhancements:
    

      

    • Set the unraisable hook as early as possible and unset it as late as possible, to collect the most possible number of unraisable exceptions.
      • 

    • Call the garbage collector just before unsetting the unraisable hook, to collect any straggling exceptions.
      • 

    • Collect multiple unraisable exceptions per test phase.
      • 

    • Report the tracemalloc{.interpreted-text role="mod"} allocation traceback (if available).
      • 

    • Avoid using a generator based hook to allow handling StopIteration{.interpreted-text role="class"} in test failures.
      • 

    • Report the unraisable exception as the cause of the pytest.PytestUnraisableExceptionWarning{.interpreted-text role="class"} exception if raised.
      • 

    • Compute the repr of the unraisable object in the unraisable hook so you get the latest information if available, and should help with resurrection of the object.
      • 

    

    • 

  • 

    #​13010: pytest.approx{.interpreted-text role="func"} now can compare collections that contain numbers and non-numbers mixed.
    

    • 

  • 

    #​13016: A number of threadexception <unraisable>{.interpreted-text role="ref"} enhancements:
    

      

    • Set the excepthook as early as possible and unset it as late as possible, to collect the most possible number of unhandled exceptions from threads.
      • 

    • Collect multiple thread exceptions per test phase.
      • 

    • Report the tracemalloc{.interpreted-text role="mod"} allocation traceback (if available).
      • 

    • Avoid using a generator based hook to allow handling StopIteration{.interpreted-text role="class"} in test failures.
      • 

    • Report the thread exception as the cause of the pytest.PytestUnhandledThreadExceptionWarning{.interpreted-text role="class"} exception if raised.
      • 

    • Extract the name of the thread object in the excepthook which should help with resurrection of the thread.
      • 

    

    • 

  • 

    #​13031: An empty parameter set as in pytest.mark.parametrize([], ids=idfunc) will no longer trigger a call to idfunc with internal objects.
    

    • 

  • 

    #​13115: Allows supplying ExceptionGroup[Exception] and BaseExceptionGroup[BaseException] to pytest.raises to keep full typing on ExceptionInfo <pytest.ExceptionInfo>{.interpreted-text role="class"}:
    

    with pytest.raises(ExceptionGroup[Exception]) as exc_info:
    some_function()
    

    Parametrizing with other exception types remains an error - we do not check the types of child exceptions and thus do not permit code that might look like we do.
    

    • 

  • 

    #​13122: The --stepwise mode received a number of improvements:
    

      

    • 

      It no longer forgets the last failed test in case pytest is executed later without the flag.
      

      This enables the following workflow:
      

        

      1. Execute pytest with --stepwise, pytest then stops at the first failing test;
        2. 

      2. Iteratively update the code and run the test in isolation, without the --stepwise flag (for example in an IDE), until it is fixed.
        3. 

      3. Execute pytest with --stepwise again and pytest will continue from the previously failed test, and if it passes, continue on to the next tests.
        4. 

      

      Previously, at step 3, pytest would start from the beginning, forgetting the previously failed test.
      

      This change however might cause issues if the --stepwise mode is used far apart in time, as the state might get stale, so the internal state will be reset automatically in case the test suite changes (for now only the number of tests are considered for this, we might change/improve this on the future).
      

      • 

    • 

      New --stepwise-reset/--sw-reset flag, allowing the user to explicitly reset the stepwise state and restart the workflow from the beginning.
      

      • 

    

    • 

  • 

    #​13308: Added official support for Python 3.14.
    

    • 

  • 

    #​13380: Fix ExceptionGroup{.interpreted-text role="class"} traceback filtering to exclude pytest internals.
    

    • 

  • 

    #​13415: The author metadata of the BibTex example is now correctly formatted with last names following first names.
    
An example of BibLaTex has been added.
    
BibTex and BibLaTex examples now clearly indicate that what is cited is software.
    

    -- by willynilly{.interpreted-text role="user"}
    

    • 

  • 

    #​13420: Improved test collection performance by optimizing path resolution used in FSCollector.
    

    • 

  • 

    #​13457: The error message about duplicate parametrization no longer displays an internal stack trace.
    

    • 

  • 

    #​4112: Using pytest.mark.usefixtures <pytest.mark.usefixtures ref>{.interpreted-text role="ref"} on pytest.param{.interpreted-text role="func"} now produces an error instead of silently doing nothing.
    

    • 

  • 

    #​5473: Replace [:]{.title-ref} with [;]{.title-ref} in the assertion rewrite warning message so it can be filtered using standard Python warning filters before calling pytest.main{.interpreted-text role="func"}.
    

    • 

  • 



[#&#8203;6985](https://redirect.github.com/pytest-dev/pytest/issues/6985): Improved `pytest.approx`{.interpreted-text role="func"} to enhance the readability of value ranges and tolerances between 0.001 and 1000.



:   -   The [repr]{.title-ref} method now provides clearer output for values within those ranges, making it easier to interpret the results.

    -   Previously, the output for those ranges of values and tolerances was displayed in scientific notation (e.g., [42 ± 1.0e+00]{.title-ref}). The updated method now presents the tolerance as a decimal for better readability (e.g., [42 ± 1]{.title-ref}).

        Example:

        **Previous Output:**

        ``` console
        >>> pytest.approx(42, abs=1)
        42 ± 1.0e+00
        ```

        **Current Output:**

        ``` console
        >>> pytest.approx(42, abs=1)
        42 ± 1
        ```

    \-- by `fazeelghafoor`{.interpreted-text role="user"}



    

  • #​7683: The formerly optional pygments dependency is now required, causing output always to be source-highlighted (unless disabled via the --code-highlight=no CLI option).
    • 



Bug fixes


    

  • 

    #​10404: Apply filterwarnings from config/cli as soon as possible, and revert them as late as possible
    
so that warnings as errors are collected throughout the pytest run and before the
    
unraisable and threadexcept hooks are removed.
    

    This allows very late warnings and unraisable/threadexcept exceptions to fail the test suite.
    

    This also changes the warning that the lsof plugin issues from PytestWarning to the new warning PytestFDWarning so it can be more easily filtered.
    

    • 

  • 

    #​11067: The test report is now consistent regardless if the test xfailed via pytest.mark.xfail <pytest.mark.xfail ref>{.interpreted-text role="ref"} or pytest.fail{.interpreted-text role="func"}.
    

    Previously, xfailed tests via the marker would have the string "reason: " prefixed to the message, while those xfailed via the function did not. The prefix has been removed.
    

    • 

  • 

    #​12008: In 11220{.interpreted-text role="pr"}, an unintended change in reordering was introduced by changing the way indices were assigned to direct params. More specifically, before that change, the indices of direct params to metafunc's callspecs were assigned after all parametrizations took place. Now, that change is reverted.
    

    • 

  • 

    #​12863: Fix applying markers, including pytest.mark.parametrize <pytest.mark.parametrize ref>{.interpreted-text role="ref"} when placed above [@​staticmethod]{.title-ref} or [@​classmethod]{.title-ref}.
    

    • 

  • 

    #​12929: Handle StopIteration from test cases, setup and teardown correctly.
    

    • 

  • 

    #​12938: Fixed --durations-min argument not respected if -vv is used.
    

    • 

  • 

    #​12946: Fixed missing help for pdb{.interpreted-text role="mod"} commands wrapped by pytest -- by adamchainz{.interpreted-text role="user"}.
    

    • 

  • 

    #​12981: Prevent exceptions in pytest.Config.add_cleanup{.interpreted-text role="func"} callbacks preventing further cleanups.
    

    • 

  • 

    #​13047: Restore pytest.approx{.interpreted-text role="func"} handling of equality checks between [bool]{.title-ref} and [numpy.bool_]{.title-ref} types.
    

    Comparing [bool]{.title-ref} and [numpy.bool_]{.title-ref} using pytest.approx{.interpreted-text role="func"} accidentally changed in version [8.3.4]{.title-ref} and [8.3.5]{.title-ref} to no longer match:
    

    >>> import numpy as np
>>> from pytest import approx
>>> [np.True_, np.True_] == pytest.approx([True, True])
False
    

    This has now been fixed:
    

    >>> [np.True_, np.True_] == pytest.approx([True, True])
True
    

    • 

  • 

    #​13119: Improved handling of invalid regex patterns for filter warnings by providing a clear error message.
    

    • 

  • 

    #​13175: The diff is now also highlighted correctly when comparing two strings.
    

    • 

  • 

    #​13248: Fixed an issue where passing a scope in Metafunc.parametrize <pytest.Metafunc.parametrize>{.interpreted-text role="py:func"} with indirect=True
    
could result in other fixtures being unable to depend on the parametrized fixture.
    

    • 

  • 

    #​13291: Fixed repr of attrs objects in assertion failure messages when using attrs>=25.2.
    

    • 

  • 

    #​13312: Fixed a possible KeyError crash on PyPy during collection of tests involving higher-scoped parameters.
    

    • 

  • 

    #​13345: Fix type hints for pytest.TestReport.when{.interpreted-text role="attr"} and pytest.TestReport.location{.interpreted-text role="attr"}.
    

    • 

  • 

    #​13377: Fixed handling of test methods with positional-only parameter syntax.
    

    Now, methods are supported that formally define self as positional-only
    
and/or fixture parameters as keyword-only, e.g.:
    

    class TestClass:

    def test_method(self, /, *, fixture): ...
    

    Before, this caused an internal error in pytest.
    

    • 

  • 

    #​13384: Fixed an issue where pytest could report negative durations.
    

    • 

  • 

    #​13420: Added lru_cache to nodes._check_initialpaths_for_relpath.
    

    • 

  • 

    #​9037: Honor disable_test_id_escaping_and_forfeit_all_rights_to_community_support{.interpreted-text role="confval"} when escaping ids in parametrized tests.
    

    • 



Improved documentation


    

  • 

    #​12535: [This
    
example]{.title-ref}<https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures>
    
showed print statements that do not exactly reflect what the
    
different branches actually do. The fix makes the example more precise.
    

    • 

  • 

    #​13218: Pointed out in the pytest.approx{.interpreted-text role="func"} documentation that it considers booleans unequal to numeric zero or one.
    

    • 

  • 

    #​13221: Improved grouping of CLI options in the --help output.
    

    • 

  • 

    #​6649: Added ~pytest.TerminalReporter{.interpreted-text role="class"} to the api-reference{.interpreted-text role="ref"} documentation page.
    

    • 

  • 

    #​8612: Add a recipe for handling abstract test classes in the documentation.
    

    A new example has been added to the documentation to demonstrate how to use a mixin class to handle abstract
    
test classes without manually setting the __test__ attribute for subclasses.
    
This ensures that subclasses of abstract test classes are automatically collected by pytest.
    

    • 



Packaging updates and notes for downstreams


    

  • #​13317: Specified minimum allowed versions of colorama, iniconfig,
    
and packaging; and bumped the minimum allowed version
    
of exceptiongroup for python_version<'3.11' from a release
    
candidate to a full release.
    • 



Contributor-facing changes


    

  • 

    #​12017: Mixed internal improvements:
    

      

    • Migrate formatting to f-strings in some tests.
      • 

    • Use type-safe constructs in JUnitXML tests.
      • 

    • MovedMockTiming into _pytest.timing.
      • 

    

    -- by RonnyPfannschmidt{.interpreted-text role="user"}
    

    • 

  • 

    #​12647: Fixed running the test suite with the hypothesis pytest plugin.
    

    • 



Miscellaneous internal changes


    

  • #​6649: Added ~pytest.TerminalReporter{.interpreted-text role="class"} to the public pytest API, as it is part of the signature of the pytest_terminal_summary{.interpreted-text role="hook"} hook.
    • 



v8.3.5


Compare Source


pytest 8.3.5 (2025-03-02)


Bug fixes


    

  • #​11777: Fixed issue where sequences were still being shortened even with -vv verbosity.
    • 

  • #​12888: Fixed broken input when using Python 3.13+ and a libedit build of Python, such as on macOS or with uv-managed Python binaries from the python-build-standalone project. This could manifest e.g. by a broken prompt when using Pdb, or seeing empty inputs with manual usage of input() and suspended capturing.
    • 

  • #​13026: Fixed AttributeError{.interpreted-text role="class"} crash when using --import-mode=importlib when top-level directory same name as another module of the standard library.
    • 

  • #​13053: Fixed a regression in pytest 8.3.4 where, when using --import-mode=importlib, a directory containing py file with the same name would cause an ImportError
    • 

  • #​13083: Fixed issue where pytest could crash if one of the collected directories got removed during collection.
    • 



Improved documentation


    

  • 

    #​12842: Added dedicated page about using types with pytest.
    

    See types{.interpreted-text role="ref"} for detailed usage.
    

    • 



Contributor-facing changes


    

  • #​13112: Fixed selftest failures in test_terminal.py with Pygments >= 2.19.0
    • 

  • #​13256: Support for Towncrier versions released in 2024 has been re-enabled
    
when building Sphinx docs -- by webknjaz{.interpreted-text role="user"}.
    • 






csernazs/pytest-httpserver (pytest-httpserver)

v1.1.3


Compare Source


=====


.. _Release Notes_1.1.3_Bug Fixes:


Bug Fixes


    

  • Run server threads with daemon flag, preventing shutdown issues.
    
#&#8203;411 <https://github.com/csernazs/pytest-httpserver/pull/411>_
    • 



.. _Release Notes_1.1.2:


v1.1.2


[Compare Source](https://redirect.gith






Configuration


📅 Schedule: Branch creation - "every 2nd week starting on the 2 week of the year before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).


🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.


♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.


👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.




    

  •  If you want to rebase/retry this PR, check this box
    • 





This PR was generated by Mend Renovate. View the repository job log.


    

  
  



      


          

          
  
  

    
  
    
    

  

  

  



          

        
      




  




      

       
            



      

  
          

  
  

  
      @renovate
  renovate
bot

          requested a review
  from a team
    as a code owner


    January 6, 2025 00:28    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
      5 times, most recently
    from
    1912918    to
    378fedd      
    Compare
  



    January 12, 2025 00:35    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
      3 times, most recently
    from
    eeefb95    to
    3106800      
    Compare
  



    January 23, 2025 06:20    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
      2 times, most recently
    from
    167c977    to
    7991b3d      
    Compare
  



    February 12, 2025 05:07    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
    from
    7991b3d    to
    36f41f2      
    Compare
  



    February 23, 2025 20:52    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
      3 times, most recently
    from
    9ad097d    to
    91ce47d      
    Compare
  



    March 9, 2025 17:08    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
    from
    91ce47d    to
    2507a07      
    Compare
  



    March 13, 2025 04:39    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
      2 times, most recently
    from
    5ba9755    to
    6831ed4      
    Compare
  



    April 1, 2025 14:58    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
      2 times, most recently
    from
    4889221    to
    8b6ba4c      
    Compare
  



    April 5, 2025 20:35    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
    from
    8b6ba4c    to
    738e6b9      
    Compare
  



    April 17, 2025 08:34    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
      2 times, most recently
    from
    935bb92    to
    7313399      
    Compare
  



    May 18, 2025 05:01    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
    from
    7313399    to
    41ddbcb      
    Compare
  



    May 22, 2025 04:48    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
      3 times, most recently
    from
    905cd1b    to
    230b751      
    Compare
  



    June 9, 2025 04:28    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
    from
    230b751    to
    ac63df3      
    Compare
  



    June 9, 2025 20:31    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
      2 times, most recently
    from
    c7ad1e7    to
    2b980db      
    Compare
  



    June 23, 2025 17:47    
    











        

  
          

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
      3 times, most recently
    from
    f90eb08    to
    6b8318d      
    Compare
  



    July 1, 2025 10:11    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
    from
    6b8318d    to
    88e3b9a      
    Compare
  



    July 22, 2025 00:15    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
      2 times, most recently
    from
    8b9613c    to
    0656d62      
    Compare
  



    August 10, 2025 15:21    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
      3 times, most recently
    from
    24f5e59    to
    2c0ded7      
    Compare
  



    August 19, 2025 12:27    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
    from
    2c0ded7    to
    20b1b3c      
    Compare
  



    August 26, 2025 00:12    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
      2 times, most recently
    from
    f6b6264    to
    3918767      
    Compare
  



    September 13, 2025 17:48    
    




  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
      3 times, most recently
    from
    2483d9b    to
    913192c      
    Compare
  



    September 23, 2025 19:07    
    




  
  

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
      2 times, most recently
    from
    0839bfd    to
    b56adb0      
    Compare
  



    November 2, 2025 19:11    
    









        

  
        





        

  
          

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/poetry


    
 branch
    from
    b56adb0    to
    a6123c9      
    Compare
  



    November 15, 2025 23:15    
    









        

  
      



  

  @renovate






  



    

      

  

    

      

          
    
    

  


        
            
  
      
              Copy link

  

        
      

    


    

        

  
    Contributor


        

  Author


    

  


  

    

      
          
      

      
            renovate
  bot

      

      

      commented


        Nov 15, 2025


      
  •

  

    
      

        
          edited
          
        
        
      

    
    
      
  
        
      Loading


  
    
  



    


  





      


        



  
    

      
          
⚠️ Artifact update problem


Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.


♻ Renovate will retry this branch, including artifacts, only when one of the following happens:


    

  • any of the package files in this branch needs updating, or
    • 

  • the branch becomes conflicted, or
    • 

  • you click the rebase/retry checkbox if found above, or
    • 

  • you rename this PR's title to start with "rebase!" to trigger it manually
    • 



The artifact failure details are included below:


File name: poetry.lock


Updating dependencies
Resolving dependencies...


The current project's supported Python range (>=3.9) is not compatible with some of the required packages Python requirement:
  - pre-commit requires Python >=3.10, so it will not be satisfied for Python >=3.9,<3.10

Because passwordless depends on pre-commit (4.4.0) which requires Python >=3.10, version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For pre-commit, a possible solution would be to set the `python` property to ">=3.10"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers




      		
    

  





        


            

            
            

              
            

        

      


      

            
  
  

    
  
    
    

  

  

  


    














  
  

    

      

  




      


    


    

      

        
      

  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment


  



      

    

  




  
          



      

  

    
    

    

  

    Reviewers
  


    

    No reviews






    

    

  


      
  

    Assignees
  



        


    No one assigned







      


  


  

    Labels
  



    

    None yet







      

  

    

        

    Projects
  


        




    None yet




  



      


  

    
  

    Milestone
  


      No milestone





    
      
          


  

    

      
        

          
  

    Development
  



            


Successfully merging this pull request may close these issues.





  
  



      
    

  




      

    

  
      

  

    

      1 participant