-
Notifications
You must be signed in to change notification settings - Fork 14
Commit 56f5416
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?v=4&size=40){kind=avatar}
chore(deps): update dependency pytest to ~=8.4.0 (#414)
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [pytest](https://redirect.github.com/pytest-dev/pytest)
([changelog](https://docs.pytest.org/en/stable/changelog.html)) |
`~=8.3.0` -> `~=8.4.0` |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
---
### Release Notes
<details>
<summary>pytest-dev/pytest (pytest)</summary>
###
[`v8.4.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/8.4.0)
[Compare
Source](https://redirect.github.com/pytest-dev/pytest/compare/8.3.5...8.4.0)
### pytest 8.4.0 (2025-06-02)
#### Removals and backward incompatible breaking changes
-
[#​11372](https://redirect.github.com/pytest-dev/pytest/issues/11372):
Async tests will now fail, instead of warning+skipping, if you don't
have any suitable plugin installed.
-
[#​12346](https://redirect.github.com/pytest-dev/pytest/issues/12346):
Tests will now fail, instead of raising a warning, if they return any
value other than None.
-
[#​12874](https://redirect.github.com/pytest-dev/pytest/issues/12874):
We dropped support for Python 3.8 following its end of life
(2024-10-07).
-
[#​12960](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/12081):
Added `capteesys`{.interpreted-text role="fixture"} to capture AND pass
output to next handler set by `--capture=`.
-
[#​12504](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/12749):
pytest traditionally collects classes/functions in the test module
namespace even if they are imported from another file.
For example:
```python
```
### 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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/13125):
`console_output_style`{.interpreted-text role="confval"} now supports
`times` to show execution time of each test.
-
[#​13192](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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.
```pytest
================================= 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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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:
```python
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:
```ini
[pytest]
int_value = 3
float_value = 5.4
```
-
[#​11525](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/12707):
Exception chains can be navigated when dropped into Pdb in Python 3.13+.
-
[#​12736](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/13010):
`pytest.approx`{.interpreted-text role="func"} now can compare
collections that contain numbers and non-numbers mixed.
-
[#​13016](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/13031):
An empty parameter set as in `pytest.mark.parametrize([], ids=idfunc)`
will no longer trigger a call to `idfunc` with internal objects.
-
[#​13115](https://redirect.github.com/pytest-dev/pytest/issues/13115):
Allows supplying `ExceptionGroup[Exception]` and
`BaseExceptionGroup[BaseException]` to `pytest.raises` to keep full
typing on `ExceptionInfo <pytest.ExceptionInfo>`{.interpreted-text
role="class"}:
```python
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](https://redirect.github.com/pytest-dev/pytest/issues/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. Iteratively update the code and run the test in isolation, without
the `--stepwise` flag (for example in an IDE), until it is fixed.
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.
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](https://redirect.github.com/pytest-dev/pytest/issues/13308):
Added official support for Python 3.14.
-
[#​13380](https://redirect.github.com/pytest-dev/pytest/issues/13380):
Fix `ExceptionGroup`{.interpreted-text role="class"} traceback filtering
to exclude pytest internals.
-
[#​13415](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/13420):
Improved test collection performance by optimizing path resolution used
in `FSCollector`.
-
[#​13457](https://redirect.github.com/pytest-dev/pytest/issues/13457):
The error message about duplicate parametrization no longer displays an
internal stack trace.
-
[#​4112](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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"}.
-
<!---->
[#​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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/12863):
Fix applying markers, including `pytest.mark.parametrize
<pytest.mark.parametrize ref>`{.interpreted-text role="ref"} when placed
above
\[[@​staticmethod](https://redirect.github.com/staticmethod)]{.title-ref}
or
\[[@​classmethod](https://redirect.github.com/classmethod)]{.title-ref}.
-
[#​12929](https://redirect.github.com/pytest-dev/pytest/issues/12929):
Handle StopIteration from test cases, setup and teardown correctly.
-
[#​12938](https://redirect.github.com/pytest-dev/pytest/issues/12938):
Fixed `--durations-min` argument not respected if `-vv` is used.
-
[#​12946](https://redirect.github.com/pytest-dev/pytest/issues/12946):
Fixed missing help for `pdb`{.interpreted-text role="mod"} commands
wrapped by pytest -- by `adamchainz`{.interpreted-text role="user"}.
-
[#​12981](https://redirect.github.com/pytest-dev/pytest/issues/12981):
Prevent exceptions in `pytest.Config.add_cleanup`{.interpreted-text
role="func"} callbacks preventing further cleanups.
-
[#​13047](https://redirect.github.com/pytest-dev/pytest/issues/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:
```pycon
>>> import numpy as np
>>> from pytest import approx
>>> [np.True_, np.True_] == pytest.approx([True, True])
False
```
This has now been fixed:
```pycon
>>> [np.True_, np.True_] == pytest.approx([True, True])
True
```
-
[#​13119](https://redirect.github.com/pytest-dev/pytest/issues/13119):
Improved handling of invalid regex patterns for filter warnings by
providing a clear error message.
-
[#​13175](https://redirect.github.com/pytest-dev/pytest/issues/13175):
The diff is now also highlighted correctly when comparing two strings.
-
[#​13248](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/13291):
Fixed `repr` of `attrs` objects in assertion failure messages when using
`attrs>=25.2`.
-
[#​13312](https://redirect.github.com/pytest-dev/pytest/issues/13312):
Fixed a possible `KeyError` crash on PyPy during collection of tests
involving higher-scoped parameters.
-
[#​13345](https://redirect.github.com/pytest-dev/pytest/issues/13345):
Fix type hints for `pytest.TestReport.when`{.interpreted-text
role="attr"} and `pytest.TestReport.location`{.interpreted-text
role="attr"}.
-
[#​13377](https://redirect.github.com/pytest-dev/pytest/issues/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.:
```python
class TestClass:
def test_method(self, /, *, fixture): ...
```
Before, this caused an internal error in pytest.
-
[#​13384](https://redirect.github.com/pytest-dev/pytest/issues/13384):
Fixed an issue where pytest could report negative durations.
-
[#​13420](https://redirect.github.com/pytest-dev/pytest/issues/13420):
Added `lru_cache` to `nodes._check_initialpaths_for_relpath`.
-
[#​9037](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/13218):
Pointed out in the `pytest.approx`{.interpreted-text role="func"}
documentation that it considers booleans unequal to numeric zero or one.
-
[#​13221](https://redirect.github.com/pytest-dev/pytest/issues/13221):
Improved grouping of CLI options in the `--help` output.
-
[#​6649](https://redirect.github.com/pytest-dev/pytest/issues/6649):
Added `~pytest.TerminalReporter`{.interpreted-text role="class"} to the
`api-reference`{.interpreted-text role="ref"} documentation page.
-
[#​8612](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/12017):
Mixed internal improvements:
- Migrate formatting to f-strings in some tests.
- Use type-safe constructs in JUnitXML tests.
- Moved`MockTiming` into `_pytest.timing`.
\-- by `RonnyPfannschmidt`{.interpreted-text role="user"}
-
[#​12647](https://redirect.github.com/pytest-dev/pytest/issues/12647):
Fixed running the test suite with the `hypothesis` pytest plugin.
#### Miscellaneous internal changes
-
[#​6649](https://redirect.github.com/pytest-dev/pytest/issues/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.
</details>
---
### Configuration
📅 **Schedule**: Branch creation - "before 7am every weekday" (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.
🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/apify/apify-client-python).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC4zMy42IiwidXBkYXRlZEluVmVyIjoiNDAuMzMuNiIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6W119-->
---------
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Josef Prochazka <[email protected]>1 parent 2a958f1 commit 56f5416Copy full SHA for 56f5416
File tree
Expand file treeCollapse file tree
3 files changed
+44
-33
lines changedFilter options
- tests/unit
Expand file treeCollapse file tree
3 files changed
+44
-33
lines changed+1-1Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
48 | 48 | | |
49 | 49 | | |
50 | 50 | | |
51 | | - | |
| 51 | + | |
52 | 52 | | |
53 | 53 | | |
54 | 54 | | |
| |||
tests/unit/test_client_errors.py
Copy file name to clipboardExpand all lines: tests/unit/test_client_errors.py+5-4Lines changed: 5 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
| 2 | + | |
2 | 3 | | |
3 | 4 | | |
4 | 5 | | |
5 | 6 | | |
6 | | - | |
7 | 7 | | |
8 | 8 | | |
9 | 9 | | |
| |||
16 | 16 | | |
17 | 17 | | |
18 | 18 | | |
19 | | - | |
20 | 19 | | |
21 | | - | |
| 20 | + | |
22 | 21 | | |
23 | 22 | | |
24 | 23 | | |
25 | | - | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
26 | 27 | | |
27 | 28 | | |
28 | 29 | | |
| |||
+38-28Lines changed: 38 additions & 28 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments