actions/checkout (actions/checkout)
### [`v4`](https://togithub.com/actions/checkout/blob/HEAD/CHANGELOG.md#v417)
[Compare Source](https://togithub.com/actions/checkout/compare/v3...v4)
- Bump the minor-npm-dependencies group across 1 directory with 4 updates by [@dependabot](https://togithub.com/dependabot) in [https://github.com/actions/checkout/pull/1739](https://togithub.com/actions/checkout/pull/1739)
- Bump actions/checkout from 3 to 4 by [@dependabot](https://togithub.com/dependabot) in [https://github.com/actions/checkout/pull/1697](https://togithub.com/actions/checkout/pull/1697)
- Check out other refs/\* by commit by [@orhantoy](https://togithub.com/orhantoy) in [https://github.com/actions/checkout/pull/1774](https://togithub.com/actions/checkout/pull/1774)
- Pin actions/checkout's own workflows to a known, good, stable version. by [@jww3](https://togithub.com/jww3) in [https://github.com/actions/checkout/pull/1776](https://togithub.com/actions/checkout/pull/1776)
### [`v3`](https://togithub.com/actions/checkout/blob/HEAD/CHANGELOG.md#v360)
[Compare Source](https://togithub.com/actions/checkout/compare/v2...v3)
- [Fix: Mark test scripts with Bash'isms to be run via Bash](https://togithub.com/actions/checkout/pull/1377)
- [Add option to fetch tags even if fetch-depth > 0](https://togithub.com/actions/checkout/pull/579)
actions/setup-python (actions/setup-python)
### [`v5`](https://togithub.com/actions/setup-python/compare/v4...v5)
[Compare Source](https://togithub.com/actions/setup-python/compare/v4...v5)
### [`v4`](https://togithub.com/actions/setup-python/compare/v3...v4)
[Compare Source](https://togithub.com/actions/setup-python/compare/v3...v4)
### [`v3`](https://togithub.com/actions/setup-python/compare/v2...v3)
[Compare Source](https://togithub.com/actions/setup-python/compare/v2...v3)
docker/docker-py (docker)
### [`v7.1.0`](https://togithub.com/docker/docker-py/releases/tag/7.1.0)
[Compare Source](https://togithub.com/docker/docker-py/compare/7.0.0...7.1.0)
#### Upgrade Notes
- Bumped minimum engine API version to 1.24
- Bumped default engine API version to 1.44 (Moby 25.0)
#### Bugfixes
- Fixed issue with tag parsing when the registry address includes ports that resulted in `invalid tag format` errors
- Fixed issue preventing creating new configs (`ConfigCollection`), which failed with a `KeyError` due to the `name` field
- Fixed an issue due to an update in the [requests](https://togithub.com/psf/requests) package breaking `docker-py` by applying the [suggested fix](https://togithub.com/psf/requests/pull/6710)
#### Miscellaneous
- Documentation improvements
- Updated Ruff (linter) and fixed minor linting issues
- Packaging/CI updates
- Started using hatch for packaging (https://github.com/pypa/hatch)
- Updated `setup-python` github action
- Updated tests
- Stopped checking for deprecated container and image related fields (`Container` and `ContainerConfig`)
- Updated tests that check `NetworkSettings.Networks..Aliases` due to engine changes
#### What's Changed
- Bump default API version to 1.43 (Moby 24.0) by [@vvoland](https://togithub.com/vvoland) in [https://github.com/docker/docker-py/pull/3199](https://togithub.com/docker/docker-py/pull/3199)
- integration/commit: Don't check for deprecated fields by [@vvoland](https://togithub.com/vvoland) in [https://github.com/docker/docker-py/pull/3203](https://togithub.com/docker/docker-py/pull/3203)
- fix: tag regex should allow ports by [@artificial-intelligence](https://togithub.com/artificial-intelligence) in [https://github.com/docker/docker-py/pull/3196](https://togithub.com/docker/docker-py/pull/3196)
- utils: Fix datetime_to_timestamp by [@vvoland](https://togithub.com/vvoland) in [https://github.com/docker/docker-py/pull/3208](https://togithub.com/docker/docker-py/pull/3208)
- fix: keyerror when creating new config([#3110](https://togithub.com/docker/docker-py/issues/3110)) by [@Khushiyant](https://togithub.com/Khushiyant) in [https://github.com/docker/docker-py/pull/3200](https://togithub.com/docker/docker-py/pull/3200)
- Update Ruff, fix some minor issues by [@akx](https://togithub.com/akx) in [https://github.com/docker/docker-py/pull/3206](https://togithub.com/docker/docker-py/pull/3206)
- docs: change image.history() return type to list ([#3076](https://togithub.com/docker/docker-py/issues/3076)) by [@Khushiyant](https://togithub.com/Khushiyant) in [https://github.com/docker/docker-py/pull/3202](https://togithub.com/docker/docker-py/pull/3202)
- lint: fix string formatting by [@milas](https://togithub.com/milas) in [https://github.com/docker/docker-py/pull/3211](https://togithub.com/docker/docker-py/pull/3211)
- Drop `packaging` dependency by [@akx](https://togithub.com/akx) in [https://github.com/docker/docker-py/pull/3205](https://togithub.com/docker/docker-py/pull/3205)
- Bump default API version to 1.44 (Moby 25.0) by [@vvoland](https://togithub.com/vvoland) in [https://github.com/docker/docker-py/pull/3231](https://togithub.com/docker/docker-py/pull/3231)
- Modernize build to use `hatchling` and `hatch-vcs` by [@akx](https://togithub.com/akx) in [https://github.com/docker/docker-py/pull/3207](https://togithub.com/docker/docker-py/pull/3207)
- Enable Ruff I (import sort), autofix by [@akx](https://togithub.com/akx) in [https://github.com/docker/docker-py/pull/3212](https://togithub.com/docker/docker-py/pull/3212)
- chore(ci): fix-ups across Make / Docker / GitHub Actions by [@milas](https://togithub.com/milas) in [https://github.com/docker/docker-py/pull/3241](https://togithub.com/docker/docker-py/pull/3241)
- chore: fix return type docs for `container.logs()` by [@BobDu](https://togithub.com/BobDu) in [https://github.com/docker/docker-py/pull/2240](https://togithub.com/docker/docker-py/pull/2240)
- CI fix by [@krissetto](https://togithub.com/krissetto) in [https://github.com/docker/docker-py/pull/3260](https://togithub.com/docker/docker-py/pull/3260)
- Fix for requests 2.32 by [@felixfontein](https://togithub.com/felixfontein) in [https://github.com/docker/docker-py/pull/3257](https://togithub.com/docker/docker-py/pull/3257)
- Added 7.1.0 changelog by [@krissetto](https://togithub.com/krissetto) in [https://github.com/docker/docker-py/pull/3262](https://togithub.com/docker/docker-py/pull/3262)
- Fix env var name in release pipeline by [@krissetto](https://togithub.com/krissetto) in [https://github.com/docker/docker-py/pull/3263](https://togithub.com/docker/docker-py/pull/3263)
- Change env var name in release pipeline to match hatch expectations by [@krissetto](https://togithub.com/krissetto) in [https://github.com/docker/docker-py/pull/3264](https://togithub.com/docker/docker-py/pull/3264)
#### New Contributors
- [@vvoland](https://togithub.com/vvoland) made their first contribution in [https://github.com/docker/docker-py/pull/3199](https://togithub.com/docker/docker-py/pull/3199)
- [@artificial-intelligence](https://togithub.com/artificial-intelligence) made their first contribution in [https://github.com/docker/docker-py/pull/3196](https://togithub.com/docker/docker-py/pull/3196)
- [@Khushiyant](https://togithub.com/Khushiyant) made their first contribution in [https://github.com/docker/docker-py/pull/3200](https://togithub.com/docker/docker-py/pull/3200)
- [@BobDu](https://togithub.com/BobDu) made their first contribution in [https://github.com/docker/docker-py/pull/2240](https://togithub.com/docker/docker-py/pull/2240)
- [@krissetto](https://togithub.com/krissetto) made their first contribution in [https://github.com/docker/docker-py/pull/3260](https://togithub.com/docker/docker-py/pull/3260)
**Full Changelog**: https://github.com/docker/docker-py/compare/7.0.0...7.1.0
### [`v7.0.0`](https://togithub.com/docker/docker-py/releases/tag/7.0.0)
[Compare Source](https://togithub.com/docker/docker-py/compare/6.1.3...7.0.0)
#### Upgrade Notes (from 6.x) ā ļø
- Removed SSL version (`ssl_version`) and explicit hostname check (`assert_hostname`) options ([#3185](https://togithub.com/docker/docker-py/issues/3185))
- `assert_hostname` has not been used since Python 3.6 and was removed in 3.12
- Python 3.7+ supports TLSv1.3 by default
- Websocket support is no longer included by default ([#3123](https://togithub.com/docker/docker-py/issues/3123))
- Use `pip install docker[websockets]` to include `websocket-client` dependency
- By default, `docker-py` hijacks the TCP connection and does not use Websockets
- Websocket client is only required to use `attach_socket(container, ws=True)`
- Python 3.7 no longer supported (reached end-of-life June 2023) ([#3187](https://togithub.com/docker/docker-py/issues/3187))
#### Features āØ
- Python 3.12 support ([#3185](https://togithub.com/docker/docker-py/issues/3185))
- Full `networking_config` support for `containers.create()` ([#3121](https://togithub.com/docker/docker-py/issues/3121))
- Replaces `network_driver_opt` (added in 6.1.0)
- Add `health()` property to container that returns status (e.g. `unhealthy`) ([#3147](https://togithub.com/docker/docker-py/issues/3147))
- Add `pause` option to `container.commit()` ([#3159](https://togithub.com/docker/docker-py/issues/3159))
- Add support for bind mount propagation (e.g. `rshared`, `private`) ([#3164](https://togithub.com/docker/docker-py/issues/3164))
- Add support for `filters`, `keep_storage`, and `all` in `prune_builds()` on API v1.39+ ([#3192](https://togithub.com/docker/docker-py/issues/3192))
#### Bugfixes š
- Consistently return `docker.errors.NotFound` on 404 responses ([#3156](https://togithub.com/docker/docker-py/issues/3156))
- Validate tag format before push ([#3191](https://togithub.com/docker/docker-py/issues/3191))
##### Miscellaneous š§
- Upgraded urllib3 version in `requirements.txt` (used for development/tests) ([#3183](https://togithub.com/docker/docker-py/issues/3183))
- Documentation typo fixes & formatting improvements ([#3130](https://togithub.com/docker/docker-py/issues/3130))
- Fixed integration test compatibility for newer Moby engine versions ([#3165](https://togithub.com/docker/docker-py/issues/3165), [#3166](https://togithub.com/docker/docker-py/issues/3166), [#3145](https://togithub.com/docker/docker-py/issues/3145), [#3169](https://togithub.com/docker/docker-py/issues/3169), [#3170](https://togithub.com/docker/docker-py/issues/3170))
- Switch to [ruff](https://togithub.com/astral-sh/ruff) for linting ([#3126](https://togithub.com/docker/docker-py/issues/3126))
#### What's Changed
- fix user_guides/multiplex.rst by [@Longin-Yu](https://togithub.com/Longin-Yu) in [https://github.com/docker/docker-py/pull/3130](https://togithub.com/docker/docker-py/pull/3130)
- tests/integration: fix flake8 failures (E721 do not compare types), and fix Dockerfile for debian "bookworm" by [@thaJeztah](https://togithub.com/thaJeztah) in [https://github.com/docker/docker-py/pull/3166](https://togithub.com/docker/docker-py/pull/3166)
- tests/integration: update some tests for updated error-messages by [@thaJeztah](https://togithub.com/thaJeztah) in [https://github.com/docker/docker-py/pull/3165](https://togithub.com/docker/docker-py/pull/3165)
- README: fix link for CI status badge by [@thaJeztah](https://togithub.com/thaJeztah) in [https://github.com/docker/docker-py/pull/3167](https://togithub.com/docker/docker-py/pull/3167)
- fix: use response.text to get string rather than bytes by [@mndeveci](https://togithub.com/mndeveci) in [https://github.com/docker/docker-py/pull/3156](https://togithub.com/docker/docker-py/pull/3156)
- feat: add pause option to commit api by [@VincentLeeMax](https://togithub.com/VincentLeeMax) in [https://github.com/docker/docker-py/pull/3159](https://togithub.com/docker/docker-py/pull/3159)
- build(deps): Bump requests from 2.28.1 to 2.31.0 by [@dependabot](https://togithub.com/dependabot) in [https://github.com/docker/docker-py/pull/3136](https://togithub.com/docker/docker-py/pull/3136)
- test: remove APT_MIRROR from Dockerfile by [@thaJeztah](https://togithub.com/thaJeztah) in [https://github.com/docker/docker-py/pull/3145](https://togithub.com/docker/docker-py/pull/3145)
- Switch linting to ruff, use f-strings, fix lint errors and possible bugs by [@akx](https://togithub.com/akx) in [https://github.com/docker/docker-py/pull/3126](https://togithub.com/docker/docker-py/pull/3126)
- integration: Fix bad subnet declaration by [@akerouanton](https://togithub.com/akerouanton) in [https://github.com/docker/docker-py/pull/3169](https://togithub.com/docker/docker-py/pull/3169)
- integration: Remove test_create_check_duplicate by [@akerouanton](https://togithub.com/akerouanton) in [https://github.com/docker/docker-py/pull/3170](https://togithub.com/docker/docker-py/pull/3170)
- Support all `Network.connect` parameters in `client.containers.run` and `client.containers.create` by [@Skazza94](https://togithub.com/Skazza94) in [https://github.com/docker/docker-py/pull/3121](https://togithub.com/docker/docker-py/pull/3121)
- feat: move websocket-client to extra dependency by [@akx](https://togithub.com/akx) in [https://github.com/docker/docker-py/pull/3123](https://togithub.com/docker/docker-py/pull/3123)
- Add health property to Containers model by [@TurnrDev](https://togithub.com/TurnrDev) in [https://github.com/docker/docker-py/pull/3147](https://togithub.com/docker/docker-py/pull/3147)
- build(deps): Bump urllib3 from 1.26.11 to 1.26.18 by [@dependabot](https://togithub.com/dependabot) in [https://github.com/docker/docker-py/pull/3183](https://togithub.com/docker/docker-py/pull/3183)
- breaking: Python 3.12 compatibility & remove custom SSL adapter by [@milas](https://togithub.com/milas) in [https://github.com/docker/docker-py/pull/3185](https://togithub.com/docker/docker-py/pull/3185)
- chore: add changelog for 7.0.0 by [@milas](https://togithub.com/milas) in [https://github.com/docker/docker-py/pull/3186](https://togithub.com/docker/docker-py/pull/3186)
- chore: remove support for Python 3.7 by [@milas](https://togithub.com/milas) in [https://github.com/docker/docker-py/pull/3187](https://togithub.com/docker/docker-py/pull/3187)
- chore: update MAINTAINERS and remove CODEOWNERS by [@milas](https://togithub.com/milas) in [https://github.com/docker/docker-py/pull/3188](https://togithub.com/docker/docker-py/pull/3188)
- chore: fix missing setuptools in CI by [@milas](https://togithub.com/milas) in [https://github.com/docker/docker-py/pull/3189](https://togithub.com/docker/docker-py/pull/3189)
- Fix [#3153](https://togithub.com/docker/docker-py/issues/3153) - Validate tag before build using OCI regex by [@LombardiDaniel](https://togithub.com/LombardiDaniel) in [https://github.com/docker/docker-py/pull/3191](https://togithub.com/docker/docker-py/pull/3191)
- feat: accept filters and keep_storage in prune_builds by [@emranbm](https://togithub.com/emranbm) in [https://github.com/docker/docker-py/pull/3192](https://togithub.com/docker/docker-py/pull/3192)
- chore: update changelog and maintainer by [@milas](https://togithub.com/milas) in [https://github.com/docker/docker-py/pull/3193](https://togithub.com/docker/docker-py/pull/3193)
#### New Contributors
- [@Longin-Yu](https://togithub.com/Longin-Yu) made their first contribution in [https://github.com/docker/docker-py/pull/3130](https://togithub.com/docker/docker-py/pull/3130)
- [@mndeveci](https://togithub.com/mndeveci) made their first contribution in [https://github.com/docker/docker-py/pull/3156](https://togithub.com/docker/docker-py/pull/3156)
- [@VincentLeeMax](https://togithub.com/VincentLeeMax) made their first contribution in [https://github.com/docker/docker-py/pull/3159](https://togithub.com/docker/docker-py/pull/3159)
- [@akerouanton](https://togithub.com/akerouanton) made their first contribution in [https://github.com/docker/docker-py/pull/3169](https://togithub.com/docker/docker-py/pull/3169)
- [@TurnrDev](https://togithub.com/TurnrDev) made their first contribution in [https://github.com/docker/docker-py/pull/3147](https://togithub.com/docker/docker-py/pull/3147)
- [@LombardiDaniel](https://togithub.com/LombardiDaniel) made their first contribution in [https://github.com/docker/docker-py/pull/3191](https://togithub.com/docker/docker-py/pull/3191)
- [@emranbm](https://togithub.com/emranbm) made their first contribution in [https://github.com/docker/docker-py/pull/3192](https://togithub.com/docker/docker-py/pull/3192)
**Full Changelog**: https://github.com/docker/docker-py/compare/6.1.3...7.0.0
pytest-dev/pytest (pytest)
### [`v8.3.2`](https://togithub.com/pytest-dev/pytest/releases/tag/8.3.2)
[Compare Source](https://togithub.com/pytest-dev/pytest/compare/8.3.1...8.3.2)
# pytest 8.3.2 (2024-07-24)
## Bug fixes
- [#12652](https://togithub.com/pytest-dev/pytest/issues/12652): Resolve regression \[conda]{.title-ref} environments where no longer being automatically detected.
\-- by `RonnyPfannschmidt`{.interpreted-text role="user"}
### [`v8.3.1`](https://togithub.com/pytest-dev/pytest/releases/tag/8.3.1)
[Compare Source](https://togithub.com/pytest-dev/pytest/compare/8.3.0...8.3.1)
# pytest 8.3.1 (2024-07-20)
The 8.3.0 release failed to include the change notes and docs for the release. This patch release remedies this. There are no other changes.
### [`v8.3.0`](https://togithub.com/pytest-dev/pytest/releases/tag/8.3.0)
[Compare Source](https://togithub.com/pytest-dev/pytest/compare/8.2.2...8.3.0)
### pytest 8.3.0 (2024-07-20)
#### New features
- [#12231](https://togithub.com/pytest-dev/pytest/issues/12231): Added \[--xfail-tb]{.title-ref} flag, which turns on traceback output for XFAIL results.
- If the \[--xfail-tb]{.title-ref} flag is not given, tracebacks for XFAIL results are NOT shown.
- The style of traceback for XFAIL is set with \[--tb]{.title-ref}, and can be \[auto|long|short|line|native|no]{.title-ref}.
- Note: Even if you have \[--xfail-tb]{.title-ref} set, you won't see them if \[--tb=no]{.title-ref}.
Some history:
With pytest 8.0, \[-rx]{.title-ref} or \[-ra]{.title-ref} would not only turn on summary reports for xfail, but also report the tracebacks for xfail results. This caused issues with some projects that utilize xfail, but don't want to see all of the xfail tracebacks.
This change detaches xfail tracebacks from \[-rx]{.title-ref}, and now we turn on xfail tracebacks with \[--xfail-tb]{.title-ref}. With this, the default \[-rx]{.title-ref}/ \[-ra]{.title-ref} behavior is identical to pre-8.0 with respect to xfail tracebacks. While this is a behavior change, it brings default behavior back to pre-8.0.0 behavior, which ultimately was considered the better course of action.
- [#12281](https://togithub.com/pytest-dev/pytest/issues/12281): Added support for keyword matching in marker expressions.
Now tests can be selected by marker keyword arguments.
Supported values are `int`{.interpreted-text role="class"}, (unescaped) `str`{.interpreted-text role="class"}, `bool`{.interpreted-text role="class"} & `None`{.interpreted-text role="data"}.
See `marker examples `{.interpreted-text role="ref"} for more information.
\-- by `lovetheguitar`{.interpreted-text role="user"}
- [#12567](https://togithub.com/pytest-dev/pytest/issues/12567): Added `--no-fold-skipped` command line option.
If this option is set, then skipped tests in short summary are no longer grouped
by reason but all tests are printed individually with their nodeid in the same
way as other statuses.
\-- by `pbrezina`{.interpreted-text role="user"}
#### Improvements in existing functionality
- [#12469](https://togithub.com/pytest-dev/pytest/issues/12469): The console output now uses the "third-party plugins" terminology,
replacing the previously established but confusing and outdated
reference to `setuptools `{.interpreted-text role="std:doc"}
\-- by `webknjaz`{.interpreted-text role="user"}.
- [#12544](https://togithub.com/pytest-dev/pytest/issues/12544), [#12545](https://togithub.com/pytest-dev/pytest/issues/12545): Python virtual environment detection was improved by
checking for a `pyvenv.cfg`{.interpreted-text role="file"} file, ensuring reliable detection on
various platforms -- by `zachsnickers`{.interpreted-text role="user"}.
- [#2871](https://togithub.com/pytest-dev/pytest/issues/2871): Do not truncate arguments to functions in output when running with \[-vvv]{.title-ref}.
- [#389](https://togithub.com/pytest-dev/pytest/issues/389): The readability of assertion introspection of bound methods has been enhanced
\-- by `farbodahm`{.interpreted-text role="user"}, `webknjaz`{.interpreted-text role="user"}, `obestwalter`{.interpreted-text role="user"}, `flub`{.interpreted-text role="user"}
and `glyphack`{.interpreted-text role="user"}.
Earlier, it was like:
```console
=================================== FAILURES ===================================
_____________________________________ test _____________________________________
def test():
> assert Help().fun() == 2
E assert 1 == 2
E + where 1 = >()
E + where > = .fun
E + where = Help()
example.py:7: AssertionError
=========================== 1 failed in 0.03 seconds ===========================
```
And now it's like:
```console
=================================== FAILURES ===================================
_____________________________________ test _____________________________________
def test():
> assert Help().fun() == 2
E assert 1 == 2
E + where 1 = fun()
E + where fun = .fun
E + where = Help()
test_local.py:13: AssertionError
=========================== 1 failed in 0.03 seconds ===========================
```
- [#7662](https://togithub.com/pytest-dev/pytest/issues/7662): Added timezone information to the testsuite timestamp in the JUnit XML report.
#### Bug fixes
- [#11706](https://togithub.com/pytest-dev/pytest/issues/11706): Fixed reporting of teardown errors in higher-scoped fixtures when using \[--maxfail]{.title-ref} or \[--stepwise]{.title-ref}.
Originally added in pytest 8.0.0, but reverted in 8.0.2 due to a regression in pytest-xdist.
This regression was fixed in pytest-xdist 3.6.1.
- [#11797](https://togithub.com/pytest-dev/pytest/issues/11797): `pytest.approx`{.interpreted-text role="func"} now correctly handles `Sequence `{.interpreted-text role="class"}-like objects.
- [#12204](https://togithub.com/pytest-dev/pytest/issues/12204), [#12264](https://togithub.com/pytest-dev/pytest/issues/12264): Fixed a regression in pytest 8.0 where tracebacks get longer and longer when multiple
tests fail due to a shared higher-scope fixture which raised -- by `bluetech`{.interpreted-text role="user"}.
Also fixed a similar regression in pytest 5.4 for collectors which raise during setup.
The fix necessitated internal changes which may affect some plugins:
- `FixtureDef.cached_result[2]` is now a tuple `(exc, tb)`
instead of `exc`.
- `SetupState.stack` failures are now a tuple `(exc, tb)`
instead of `exc`.
- [#12275](https://togithub.com/pytest-dev/pytest/issues/12275): Fixed collection error upon encountering an `abstract `{.interpreted-text role="mod"} class, including abstract \[unittest.TestCase]{.title-ref} subclasses.
- [#12328](https://togithub.com/pytest-dev/pytest/issues/12328): Fixed a regression in pytest 8.0.0 where package-scoped parameterized items were not correctly reordered to minimize setups/teardowns in some cases.
- [#12424](https://togithub.com/pytest-dev/pytest/issues/12424): Fixed crash with \[assert testcase is not None]{.title-ref} assertion failure when re-running unittest tests using plugins like pytest-rerunfailures. Regressed in 8.2.2.
- [#12472](https://togithub.com/pytest-dev/pytest/issues/12472): Fixed a crash when returning category `"error"` or `"failed"` with a custom test status from `pytest_report_teststatus`{.interpreted-text role="hook"} hook -- `pbrezina`{.interpreted-text role="user"}.
- [#12505](https://togithub.com/pytest-dev/pytest/issues/12505): Improved handling of invalid regex patterns in `pytest.raises(match=r'...') `{.interpreted-text role="func"} by providing a clear error message.
- [#12580](https://togithub.com/pytest-dev/pytest/issues/12580): Fixed a crash when using the cache class on Windows and the cache directory was created concurrently.
- [#6962](https://togithub.com/pytest-dev/pytest/issues/6962): Parametrization parameters are now compared using \[==]{.title-ref} instead of \[is]{.title-ref} (\[is]{.title-ref} is still used as a fallback if the parameter does not support \[==]{.title-ref}).
This fixes use of parameters such as lists, which have a different \[id]{.title-ref} but compare equal, causing fixtures to be re-computed instead of being cached.
- [#7166](https://togithub.com/pytest-dev/pytest/issues/7166): Fixed progress percentages (the `[ 87%]` at the edge of the screen) sometimes not aligning correctly when running with pytest-xdist `-n`.
#### Improved documentation
- [#12153](https://togithub.com/pytest-dev/pytest/issues/12153): Documented using `PYTEST_VERSION`{.interpreted-text role="envvar"} to detect if code is running from within a pytest run.
- [#12469](https://togithub.com/pytest-dev/pytest/issues/12469): The external plugin mentions in the documentation now avoid mentioning
`setuptools entry-points `{.interpreted-text role="std:doc"} as the concept is
much more generic nowadays. Instead, the terminology of "external",
"installed", or "third-party" plugins (or packages) replaces that.
\-- by `webknjaz`{.interpreted-text role="user"}
- [#12577](https://togithub.com/pytest-dev/pytest/issues/12577): \[CI]{.title-ref} and \[BUILD_NUMBER]{.title-ref} environment variables role is discribed in
the reference doc. They now also appear when doing \[pytest -h]{.title-ref}
\-- by `MarcBresson`{.interpreted-text role="user"}.
#### Contributor-facing changes
- [#12467](https://togithub.com/pytest-dev/pytest/issues/12467): Migrated all internal type-annotations to the python3.10+ style by using the \[annotations]{.title-ref} future import.
\-- by `RonnyPfannschmidt`{.interpreted-text role="user"}
- [#11771](https://togithub.com/pytest-dev/pytest/issues/11771), [#12557](https://togithub.com/pytest-dev/pytest/issues/12557): The PyPy runtime version has been updated to 3.9 from 3.8 that introduced
a flaky bug at the garbage collector which was not expected to fix there
as the 3.8 is EoL.
\-- by `x612skm`{.interpreted-text role="user"}
- [#12493](https://togithub.com/pytest-dev/pytest/issues/12493): The change log draft preview integration has been refactored to use a
third party extension `sphinxcontib-towncrier`. The previous in-repo
script was putting the change log preview file at
`doc/en/_changelog_towncrier_draft.rst`{.interpreted-text role="file"}. Said file is no longer
ignored in Git and might show up among untracked files in the
development environments of the contributors. To address that, the
contributors can run the following command that will clean it up:
```console
$ git clean -x -i -- doc/en/_changelog_towncrier_draft.rst
```
\-- by `webknjaz`{.interpreted-text role="user"}
- [#12498](https://togithub.com/pytest-dev/pytest/issues/12498): All the undocumented `tox` environments now have descriptions.
They can be listed in one's development environment by invoking
`tox -av` in a terminal.
\-- by `webknjaz`{.interpreted-text role="user"}
- [#12501](https://togithub.com/pytest-dev/pytest/issues/12501): The changelog configuration has been updated to introduce more accurate
audience-tailored categories. Previously, there was a `trivial`
change log fragment type with an unclear and broad meaning. It was
removed and we now have `contrib`, `misc` and `packaging` in
place of it.
The new change note types target the readers who are downstream
packagers and project contributors. Additionally, the miscellaneous
section is kept for unspecified updates that do not fit anywhere else.
\-- by `webknjaz`{.interpreted-text role="user"}
- [#12502](https://togithub.com/pytest-dev/pytest/issues/12502): The UX of the GitHub automation making pull requests to update the
plugin list has been updated. Previously, the maintainers had to close
the automatically created pull requests and re-open them to trigger the
CI runs. From now on, they only need to click the \[Ready for review]{.title-ref}
button instead.
\-- by `webknjaz`{.interpreted-text role="user"}
- [#12522](https://togithub.com/pytest-dev/pytest/issues/12522): The `:pull:` RST role has been replaced with a shorter
`:pr:` due to starting to use the implementation from
the third-party `sphinx-issues`{.interpreted-text role="pypi"} Sphinx extension
\-- by `webknjaz`{.interpreted-text role="user"}.
- [#12531](https://togithub.com/pytest-dev/pytest/issues/12531): The coverage reporting configuration has been updated to exclude
pytest's own tests marked as expected to fail from the coverage
report. This has an effect of reducing the influence of flaky
tests on the resulting number.
\-- by `webknjaz`{.interpreted-text role="user"}
- [#12533](https://togithub.com/pytest-dev/pytest/issues/12533): The `extlinks` Sphinx extension is no longer enabled. The `:bpo:`
role it used to declare has been removed with that. BPO itself has
migrated to GitHub some years ago and it is possible to link the
respective issues by using their GitHub issue numbers and the
`:issue:` role that the `sphinx-issues` extension implements.
\-- by `webknjaz`{.interpreted-text role="user"}
- [#12562](https://togithub.com/pytest-dev/pytest/issues/12562): Possible typos in using the `:user:` RST role is now being linted
through the pre-commit tool integration -- by `webknjaz`{.interpreted-text role="user"}.
### [`v8.2.2`](https://togithub.com/pytest-dev/pytest/releases/tag/8.2.2)
[Compare Source](https://togithub.com/pytest-dev/pytest/compare/8.2.1...8.2.2)
# pytest 8.2.2 (2024-06-04)
## Bug Fixes
- [#12355](https://togithub.com/pytest-dev/pytest/issues/12355): Fix possible catastrophic performance slowdown on a certain parametrization pattern involving many higher-scoped parameters.
- [#12367](https://togithub.com/pytest-dev/pytest/issues/12367): Fix a regression in pytest 8.2.0 where unittest class instances (a fresh one is created for each test) were not released promptly on test teardown but only on session teardown.
- [#12381](https://togithub.com/pytest-dev/pytest/issues/12381): Fix possible "Directory not empty" crashes arising from concurent cache dir (`.pytest_cache`) creation. Regressed in pytest 8.2.0.
## Improved Documentation
- [#12290](https://togithub.com/pytest-dev/pytest/issues/12290): Updated Sphinx theme to use Furo instead of Flask, enabling Dark mode theme.
- [#12356](https://togithub.com/pytest-dev/pytest/issues/12356): Added a subsection to the documentation for debugging flaky tests to mention
lack of thread safety in pytest as a possible source of flakyness.
- [#12363](https://togithub.com/pytest-dev/pytest/issues/12363): The documentation webpages now links to a canonical version to reduce outdated documentation in search engine results.
### [`v8.2.1`](https://togithub.com/pytest-dev/pytest/releases/tag/8.2.1)
[Compare Source](https://togithub.com/pytest-dev/pytest/compare/8.2.0...8.2.1)
# pytest 8.2.1 (2024-05-19)
## Improvements
- [#12334](https://togithub.com/pytest-dev/pytest/issues/12334): Support for Python 3.13 (beta1 at the time of writing).
## Bug Fixes
- [#12120](https://togithub.com/pytest-dev/pytest/issues/12120): Fix \[PermissionError]{.title-ref} crashes arising from directories which are not selected on the command-line.
- [#12191](https://togithub.com/pytest-dev/pytest/issues/12191): Keyboard interrupts and system exits are now properly handled during the test collection.
- [#12300](https://togithub.com/pytest-dev/pytest/issues/12300): Fixed handling of 'Function not implemented' error under squashfuse_ll, which is a different way to say that the mountpoint is read-only.
- [#12308](https://togithub.com/pytest-dev/pytest/issues/12308): Fix a regression in pytest 8.2.0 where the permissions of automatically-created `.pytest_cache` directories became `rwx------` instead of the expected `rwxr-xr-x`.
## Trivial/Internal Changes
- [#12333](https://togithub.com/pytest-dev/pytest/issues/12333): pytest releases are now attested using the recent [Artifact Attestation](https://github.blog/2024-05-02-introducing-artifact-attestations-now-in-public-beta/) support from GitHub, allowing users to verify the provenance of pytest's sdist and wheel artifacts.
### [`v8.2.0`](https://togithub.com/pytest-dev/pytest/releases/tag/8.2.0)
[Compare Source](https://togithub.com/pytest-dev/pytest/compare/8.1.2...8.2.0)
# pytest 8.2.0 (2024-04-27)
## Deprecations
- [#12069](https://togithub.com/pytest-dev/pytest/issues/12069): A deprecation warning is now raised when implementations of one of the following hooks request a deprecated `py.path.local` parameter instead of the `pathlib.Path` parameter which replaced it:
- `pytest_ignore_collect`{.interpreted-text role="hook"} - the `path` parameter - use `collection_path` instead.
- `pytest_collect_file`{.interpreted-text role="hook"} - the `path` parameter - use `file_path` instead.
- `pytest_pycollect_makemodule`{.interpreted-text role="hook"} - the `path` parameter - use `module_path` instead.
- `pytest_report_header`{.interpreted-text role="hook"} - the `startdir` parameter - use `start_path` instead.
- `pytest_report_collectionfinish`{.interpreted-text role="hook"} - the `startdir` parameter - use `start_path` instead.
The replacement parameters are available since pytest 7.0.0.
The old parameters will be removed in pytest 9.0.0.
See `legacy-path-hooks-deprecated`{.interpreted-text role="ref"} for more details.
## Features
- [#11871](https://togithub.com/pytest-dev/pytest/issues/11871): Added support for reading command line arguments from a file using the prefix character `@`, like e.g.: `pytest @tests.txt`. The file must have one argument per line.
See `Read arguments from file `{.interpreted-text role="ref"} for details.
## Improvements
- [#11523](https://togithub.com/pytest-dev/pytest/issues/11523): `pytest.importorskip`{.interpreted-text role="func"} will now issue a warning if the module could be found, but raised `ImportError`{.interpreted-text role="class"} instead of `ModuleNotFoundError`{.interpreted-text role="class"}.
The warning can be suppressed by passing `exc_type=ImportError` to `pytest.importorskip`{.interpreted-text role="func"}.
See `import-or-skip-import-error`{.interpreted-text role="ref"} for details.
- [#11728](https://togithub.com/pytest-dev/pytest/issues/11728): For `unittest`-based tests, exceptions during class cleanup (as raised by functions registered with `TestCase.addClassCleanup `{.interpreted-text role="meth"}) are now reported instead of silently failing.
- [#11777](https://togithub.com/pytest-dev/pytest/issues/11777): Text is no longer truncated in the `short test summary info` section when `-vv` is given.
- [#12112](https://togithub.com/pytest-dev/pytest/issues/12112): Improved namespace packages detection when `consider_namespace_packages`{.interpreted-text role="confval"} is enabled, covering more situations (like editable installs).
- [#9502](https://togithub.com/pytest-dev/pytest/issues/9502): Added `PYTEST_VERSION`{.interpreted-text role="envvar"} environment variable which is defined at the start of the pytest session and undefined afterwards. It contains the value of `pytest.__version__`, and among other things can be used to easily check if code is running from within a pytest run.
## Bug Fixes
- [#12065](https://togithub.com/pytest-dev/pytest/issues/12065): Fixed a regression in pytest 8.0.0 where test classes containing `setup_method` and tests using `@staticmethod` or `@classmethod` would crash with `AttributeError: 'NoneType' object has no attribute 'setup_method'`.
Now the `request.instance `{.interpreted-text role="attr"} attribute of tests using `@staticmethod` and `@classmethod` is no longer `None`, but a fresh instance of the class, like in non-static methods.
Previously it was `None`, and all fixtures of such tests would share a single `self`.
- [#12135](https://togithub.com/pytest-dev/pytest/issues/12135): Fixed issue where fixtures adding their finalizer multiple times to fixtures they request would cause unreliable and non-intuitive teardown ordering in some instances.
- [#12194](https://togithub.com/pytest-dev/pytest/issues/12194): Fixed a bug with `--importmode=importlib` and `--doctest-modules` where child modules did not appear as attributes in parent modules.
- [#1489](https://togithub.com/pytest-dev/pytest/issues/1489): Fixed some instances where teardown of higher-scoped fixtures was not happening in the reverse order they were initialized in.
## Trivial/Internal Changes
- [#12069](https://togithub.com/pytest-dev/pytest/issues/12069): `pluggy>=1.5.0` is now required.
- [#12167](https://togithub.com/pytest-dev/pytest/issues/12167): `cache `{.interpreted-text role="ref"}: create supporting files (`CACHEDIR.TAG`, `.gitignore`, etc.) in a temporary directory to provide atomic semantics.
### [`v8.1.2`](https://togithub.com/pytest-dev/pytest/releases/tag/8.1.2)
[Compare Source](https://togithub.com/pytest-dev/pytest/compare/8.1.1...8.1.2)
# pytest 8.1.2 (2024-04-26)
## Bug Fixes
- [#12114](https://togithub.com/pytest-dev/pytest/issues/12114): Fixed error in `pytest.approx`{.interpreted-text role="func"} when used with \[numpy]{.title-ref} arrays and comparing with other types.
### [`v8.1.1`](https://togithub.com/pytest-dev/pytest/releases/tag/8.1.1)
[Compare Source](https://togithub.com/pytest-dev/pytest/compare/8.1.0...8.1.1)
# pytest 8.1.1 (2024-03-08)
::: {.note}
::: {.title}
Note
:::
This release is not a usual bug fix release -- it contains features and improvements, being a follow up
to `8.1.0`, which has been yanked from PyPI.
:::
## Features
- [#11475](https://togithub.com/pytest-dev/pytest/issues/11475): Added the new `consider_namespace_packages`{.interpreted-text role="confval"} 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://togithub.com/pytest-dev/pytest/issues/11653): Added the new `verbosity_test_cases`{.interpreted-text role="confval"} configuration option for fine-grained control of test execution verbosity.
See `Fine-grained verbosity `{.interpreted-text role="ref"} for more details.
## Improvements
- [#10865](https://togithub.com/pytest-dev/pytest/issues/10865): `pytest.warns`{.interpreted-text role="func"} now validates that `warnings.warn`{.interpreted-text role="func"} was called with a \[str]{.title-ref} or a \[Warning]{.title-ref}.
Currently in Python it is possible to use other types, however this causes an exception when `warnings.filterwarnings`{.interpreted-text role="func"} is used to filter those warnings (see [CPython #103577](https://togithub.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://togithub.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 `AssertionError`{.interpreted-text role="class"}.
- [#11475](https://togithub.com/pytest-dev/pytest/issues/11475): `--import-mode=importlib `{.interpreted-text role="ref"} now tries to import modules using the standard import mechanism (but still without changing :py`sys.path`{.interpreted-text role="data"}), 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://togithub.com/pytest-dev/pytest/issues/11801): Added the `iter_parents() <_pytest.nodes.Node.iter_parents>`{.interpreted-text role="func"} helper method on nodes.
It is similar to `listchain <_pytest.nodes.Node.listchain>`{.interpreted-text role="func"}, but goes from bottom to top, and returns an iterator, not a list.
- [#11850](https://togithub.com/pytest-dev/pytest/issues/11850): Added support for `sys.last_exc`{.interpreted-text role="data"} for post-mortem debugging on Python>=3.12.
- [#11962](https://togithub.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://togithub.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://togithub.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
- [#11475](https://togithub.com/pytest-dev/pytest/issues/11475): Fixed regression where `--importmode=importlib` would import non-test modules more than once.
- [#11904](https://togithub.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 `12043`{.interpreted-text role="pull"} for a comparison with pytest 8.0 and <8.
- [#12011](https://togithub.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://togithub.com/pytest-dev/pytest/issues/12014): Fix the `stacklevel` used when warning about marks used on fixtures.
- [#12039](https://togithub.com/pytest-dev/pytest/issues/12039): Fixed a regression in `8.0.2` where tests created using `tmp_path`{.interpreted-text role="fixture"} have been collected multiple times in CI under Windows.
## Improved Documentation
- [#11790](https://togithub.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://togithub.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.
- [#12069](https://togithub.com/pytest-dev/pytest/issues/12069): Delayed the deprecation of the following features to `9.0.0`:
- `node-ctor-fspath-deprecation`{.interpreted-text role="ref"}.
- `legacy-path-hooks-deprecated`{.interpreted-text role="ref"}.
It was discovered after `8.1.0` was released that the warnings about the impeding removal were not being displayed, so the team decided to revert the removal.
This is the reason for `8.1.0` being yanked.
# pytest 8.1.0 (YANKED)
::: {.note}
::: {.title}
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://togithub.com/pytest-dev/pytest/issues/12069).
:::
### [`v8.1.0`](https://togithub.com/pytest-dev/pytest/releases/tag/8.1.0)
[Compare Source](https://togithub.com/pytest-dev/pytest/compare/8.0.2...8.1.0)
# pytest 8.1.0 (YANKED)
> \[!IMPORTANT]\
> 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://togithub.com/pytest-dev/pytest/issues/12069).
## Features
- [#11475](https://togithub.com/pytest-dev/pytest/issues/11475): Added the new `consider_namespace_packages`{.interpreted-text role="confval"} 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://togithub.com/pytest-dev/pytest/issues/11653): Added the new `verbosity_test_cases`{.interpreted-text role="confval"} configuration option for fine-grained control of test execution verbosity.
See `Fine-grained verbosity `{.interpreted-text role="ref"} for more details.
## Improvements
- [#10865](https://togithub.com/pytest-dev/pytest/issues/10865): `pytest.warns`{.interpreted-text role="func"} now validates that `warnings.warn`{.interpreted-text role="func"} was called with a \[str]{.title-ref} or a \[Warning]{.title-ref}.
Currently in Python it is possible to use other types, however this causes an exception when `warnings.filterwarnings`{.interpreted-text role="func"} is used to filter those warnings (see [CPython #103577](https://togithub.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://togithub.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 `AssertionError`{.interpreted-text role="class"}.
- [#11475](https://togithub.com/pytest-dev/pytest/issues/11475): `--import-mode=importlib `{.interpreted-text role="ref"} now tries to import modules using the standard import mechanism (but still without changing :py`sys.path`{.interpreted-text role="data"}), 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://togithub.com/pytest-dev/pytest/issues/11801): Added the `iter_parents() <_pytest.nodes.Node.iter_parents>`{.interpreted-text role="func"} helper method on nodes.
It is similar to `listchain <_pytest.nodes.Node.listchain>`{.interpreted-text role="func"}, but goes from bottom to top, and returns an iterator, not a list.
- [#11850](https://togithub.com/pytest-dev/pytest/issues/11850): Added support for `sys.last_exc`{.interpreted-text role="data"} for post-mortem debugging on Python>=3.12.
- [#11962](https://togithub.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://togithub.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://togithub.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://togithub.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 `12043`{.interpreted-text role="pull"} for a comparison with pytest 8.0 and <8.
- [#12011](https://togithub.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://togithub.com/pytest-dev/pytest/issues/12014): Fix the `stacklevel` used when warning about marks used on fixtures.
- [#12039](https://togithub.com/pytest-dev/pytest/issues/12039): Fixed a regression in `8.0.2` where tests created using `tmp_path`{.interpreted-text role="fixture"} have been collected multiple times in CI under Windows.
## Improved Documentation
- [#11790](https://togithub.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://togithub.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.
### [`v8.0.2`](https://togithub.com/pytest-dev/pytest/releases/tag/8.0.2)
[Compare Source](https://togithub.com/pytest-dev/pytest/compare/8.0.1...8.0.2)
# pytest 8.0.2 (2024-02-24)
## Bug Fixes
- [#11895](https://togithub.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://togithub.com/pytest-dev/pytest/issues/11953): Fix an `IndexError` crash raising from `getstatementrange_ast`.
- [#12021](https://togithub.com/pytest-dev/pytest/issues/12021): Reverted a fix to \[--maxfail]{.title-ref} 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.
### [`v8.0.1`](https://togithub.com/pytest-dev/pytest/releases/tag/8.0.1)
[Compare Source](https://togithub.com
Configuration
š Schedule: Branch creation - "every weekend" (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 contains the following updates:
v2
->v4
v2
->v5
~=6.1.3
->~=7.1.0
~=7.1.2
->~=8.3.2
~=2.31.0
->~=2.32.3
~=68.2.2
->~=74.1.2
By merging this PR, the issue #67 will be automatically resolved and closed:
Release Notes
actions/checkout (actions/checkout)
### [`v4`](https://togithub.com/actions/checkout/blob/HEAD/CHANGELOG.md#v417) [Compare Source](https://togithub.com/actions/checkout/compare/v3...v4) - Bump the minor-npm-dependencies group across 1 directory with 4 updates by [@dependabot](https://togithub.com/dependabot) in [https://github.com/actions/checkout/pull/1739](https://togithub.com/actions/checkout/pull/1739) - Bump actions/checkout from 3 to 4 by [@dependabot](https://togithub.com/dependabot) in [https://github.com/actions/checkout/pull/1697](https://togithub.com/actions/checkout/pull/1697) - Check out other refs/\* by commit by [@orhantoy](https://togithub.com/orhantoy) in [https://github.com/actions/checkout/pull/1774](https://togithub.com/actions/checkout/pull/1774) - Pin actions/checkout's own workflows to a known, good, stable version. by [@jww3](https://togithub.com/jww3) in [https://github.com/actions/checkout/pull/1776](https://togithub.com/actions/checkout/pull/1776) ### [`v3`](https://togithub.com/actions/checkout/blob/HEAD/CHANGELOG.md#v360) [Compare Source](https://togithub.com/actions/checkout/compare/v2...v3) - [Fix: Mark test scripts with Bash'isms to be run via Bash](https://togithub.com/actions/checkout/pull/1377) - [Add option to fetch tags even if fetch-depth > 0](https://togithub.com/actions/checkout/pull/579)actions/setup-python (actions/setup-python)
### [`v5`](https://togithub.com/actions/setup-python/compare/v4...v5) [Compare Source](https://togithub.com/actions/setup-python/compare/v4...v5) ### [`v4`](https://togithub.com/actions/setup-python/compare/v3...v4) [Compare Source](https://togithub.com/actions/setup-python/compare/v3...v4) ### [`v3`](https://togithub.com/actions/setup-python/compare/v2...v3) [Compare Source](https://togithub.com/actions/setup-python/compare/v2...v3)docker/docker-py (docker)
### [`v7.1.0`](https://togithub.com/docker/docker-py/releases/tag/7.1.0) [Compare Source](https://togithub.com/docker/docker-py/compare/7.0.0...7.1.0) #### Upgrade Notes - Bumped minimum engine API version to 1.24 - Bumped default engine API version to 1.44 (Moby 25.0) #### Bugfixes - Fixed issue with tag parsing when the registry address includes ports that resulted in `invalid tag format` errors - Fixed issue preventing creating new configs (`ConfigCollection`), which failed with a `KeyError` due to the `name` field - Fixed an issue due to an update in the [requests](https://togithub.com/psf/requests) package breaking `docker-py` by applying the [suggested fix](https://togithub.com/psf/requests/pull/6710) #### Miscellaneous - Documentation improvements - Updated Ruff (linter) and fixed minor linting issues - Packaging/CI updates - Started using hatch for packaging (https://github.com/pypa/hatch) - Updated `setup-python` github action - Updated tests - Stopped checking for deprecated container and image related fields (`Container` and `ContainerConfig`) - Updated tests that check `NetworkSettings.Networks.pytest-dev/pytest (pytest)
### [`v8.3.2`](https://togithub.com/pytest-dev/pytest/releases/tag/8.3.2) [Compare Source](https://togithub.com/pytest-dev/pytest/compare/8.3.1...8.3.2) # pytest 8.3.2 (2024-07-24) ## Bug fixes - [#12652](https://togithub.com/pytest-dev/pytest/issues/12652): Resolve regression \[conda]{.title-ref} environments where no longer being automatically detected. \-- by `RonnyPfannschmidt`{.interpreted-text role="user"} ### [`v8.3.1`](https://togithub.com/pytest-dev/pytest/releases/tag/8.3.1) [Compare Source](https://togithub.com/pytest-dev/pytest/compare/8.3.0...8.3.1) # pytest 8.3.1 (2024-07-20) The 8.3.0 release failed to include the change notes and docs for the release. This patch release remedies this. There are no other changes. ### [`v8.3.0`](https://togithub.com/pytest-dev/pytest/releases/tag/8.3.0) [Compare Source](https://togithub.com/pytest-dev/pytest/compare/8.2.2...8.3.0) ### pytest 8.3.0 (2024-07-20) #### New features - [#12231](https://togithub.com/pytest-dev/pytest/issues/12231): Added \[--xfail-tb]{.title-ref} flag, which turns on traceback output for XFAIL results. - If the \[--xfail-tb]{.title-ref} flag is not given, tracebacks for XFAIL results are NOT shown. - The style of traceback for XFAIL is set with \[--tb]{.title-ref}, and can be \[auto|long|short|line|native|no]{.title-ref}. - Note: Even if you have \[--xfail-tb]{.title-ref} set, you won't see them if \[--tb=no]{.title-ref}. Some history: With pytest 8.0, \[-rx]{.title-ref} or \[-ra]{.title-ref} would not only turn on summary reports for xfail, but also report the tracebacks for xfail results. This caused issues with some projects that utilize xfail, but don't want to see all of the xfail tracebacks. This change detaches xfail tracebacks from \[-rx]{.title-ref}, and now we turn on xfail tracebacks with \[--xfail-tb]{.title-ref}. With this, the default \[-rx]{.title-ref}/ \[-ra]{.title-ref} behavior is identical to pre-8.0 with respect to xfail tracebacks. While this is a behavior change, it brings default behavior back to pre-8.0.0 behavior, which ultimately was considered the better course of action. - [#12281](https://togithub.com/pytest-dev/pytest/issues/12281): Added support for keyword matching in marker expressions. Now tests can be selected by marker keyword arguments. Supported values are `int`{.interpreted-text role="class"}, (unescaped) `str`{.interpreted-text role="class"}, `bool`{.interpreted-text role="class"} & `None`{.interpreted-text role="data"}. See `marker examplesConfiguration
š Schedule: Branch creation - "every weekend" (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.