📦 Pass desired release to PEP 517 tox env by webknjaz · Pull Request #13933 · pytest-dev/pytest

webknjaz · 2025-11-11T18:36:26Z

This patch fixes passing the release version string from the release automation script to the tox's PEP 517 frontend, so that the backend machinery bits (namely, setuptools-scm) could access the environment variable; as indentified in the attempt to release pytest v9.0.1 [1].

The solution uses the [pkgenv] section of tox.ini that corresponds to the PEP 517 build env tox manages internally.

This patch fixes passing the release version string from the release automation script to the tox's PEP 517 frontend, so that the backend machinery bits (namely, `setuptools-scm`) could access the environment variable; as indentified in the attempt to release pytest v9.0.1 [[1]]. The solution uses the `[pkgenv]` section of `tox.ini` that corresponds to the PEP 517 build env tox manages internally. [1]: https://github.com/pytest-dev/pytest/pull/13928/files#r2514197778

webknjaz · 2025-11-11T18:46:52Z

changelog/13933.contrib.rst

📚 https://pytest--13933.org.readthedocs.build/en/13933/changelog.html#packaging-updates-and-notes-for-downstreams

Copilot

Pull Request Overview

This PR fixes the release automation to properly pass the version string to the PEP 517 build environment managed by Tox. The key issue was that setuptools-scm needs access to the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST environment variable during the wheel build process, not just during test execution.

Moved SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST from [testenv] to [pkgenv] section to make it available during PEP 517 build
Removed redundant passenv declarations from specific testenvs ([testenv] and [testenv:regen])
Added comprehensive documentation comments explaining the [pkgenv] section usage and workarounds for tox v4.14.1 regression

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
tox.ini	Restructured environment variable passing to make version string available in PEP 517 build environment instead of only in test environments
changelog/13933.packaging.rst	Added changelog entry for the packaging fix (contains an error in content)
changelog/13933.contrib.rst	Contains the actual changelog content describing the tox configuration change

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

changelog/13933.packaging.rst

changelog/13933.contrib.rst

bluetech

Thanks for investigating this!

bluetech · 2025-11-11T19:02:25Z

tox.ini

+# * https://github.com/tox-dev/tox/pull/3237
+# * https://github.com/tox-dev/tox/issues/3238
+# * https://github.com/tox-dev/tox/issues/3292
+# * https://hynek.me/articles/turbo-charge-tox/


Hmm I learned through this article that we might not need coverage-enable-subprocess anymore. I think I'll try it.

@bluetech not sure but I tend to use pytest-cov that definitely doesn't.

webknjaz · 2025-11-11T19:06:23Z

Thanks for investigating this!

FTR, I'm looking more into this and the change might be incomplete.

webknjaz · 2025-11-11T19:17:22Z

I made an experimental branch here, in the upstream repo and triggered the workflow from it: https://github.com/pytest-dev/pytest/actions/runs/19276090877/job/55116123406. I cherry-picked this change in there on top of 9.0.x — let's see how it performs before merging.

webknjaz · 2025-11-11T19:24:38Z

Urgh.. I didn't trigger it the right way. Here's a proper run: https://github.com/pytest-dev/pytest/actions/runs/19276169030/job/55116378101#step:5:406. It does help with the docs diff.
And it also uses the right version in the inner tox invocation (the one running regen): https://github.com/pytest-dev/pytest/actions/runs/19276169030/job/55116378101#step:5:100.

The outer invocation still uses the Git-generated version: https://github.com/pytest-dev/pytest/actions/runs/19276169030/job/55116378101#step:5:24. But that is to be expected — the job itself invoking tox directly doesn't set this var.

webknjaz · 2025-11-11T19:25:59Z

Oh, it actually updated the existing release PR, proving that this works: https://github.com/pytest-dev/pytest/pull/13928/files#diff-0e43a7f1313ac690564ffafd9a994c5a7faba686ad62c2ea327dab13614dfc8cR23.

patchback · 2025-11-11T19:28:46Z

Backport to 9.0.x: 💚 backport PR created

✅ Backport PR branch: patchback/backports/9.0.x/ce8b8a7b4b360ac5f3953b8c3b8b59e6bb420f37/pr-13933

Backported as #13935

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

…tuptools-scm-pretend-env-var 📦 Pass desired release to PEP 517 tox env (cherry picked from commit ce8b8a7)

…e8b8a7b4b360ac5f3953b8c3b8b59e6bb420f37/pr-13933 [PR #13933/ce8b8a7b backport][9.0.x] 📦 Pass desired release to PEP 517 tox env

This MR contains the following updates: | Package | Type | Update | Change | OpenSSF | |---|---|---|---|---| | [pytest](https://github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html)) | test | major | `^8.2.0` → `^9.0.0` | [![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/pytest-dev/pytest/badge)](https://securityscorecards.dev/viewer/?uri=github.com/pytest-dev/pytest) | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.0.2`](https://github.com/pytest-dev/pytest/releases/tag/9.0.2) [Compare Source](pytest-dev/pytest@9.0.1...9.0.2) ### pytest 9.0.2 (2025-12-06) #### Bug fixes - [#13896](pytest-dev/pytest#13896): The terminal progress feature added in pytest 9.0.0 has been disabled by default, except on Windows, due to compatibility issues with some terminal emulators. You may enable it again by passing `-p terminalprogress`. We may enable it by default again once compatibility improves in the future. Additionally, when the environment variable `TERM` is `dumb`, the escape codes are no longer emitted, even if the plugin is enabled. - [#13904](pytest-dev/pytest#13904): Fixed the TOML type of the `tmp_path_retention_count` settings in the API reference from number to string. - [#13946](pytest-dev/pytest#13946): The private `config.inicfg` attribute was changed in a breaking manner in pytest 9.0.0. Due to its usage in the ecosystem, it is now restored to working order using a compatibility shim. It will be deprecated in pytest 9.1 and removed in pytest 10. - [#13965](pytest-dev/pytest#13965): Fixed quadratic-time behavior when handling `unittest` subtests in Python 3.10. #### Improved documentation - [#4492](pytest-dev/pytest#4492): The API Reference now contains cross-reference-able documentation of `pytest's command-line flags <command-line-flags>`. ### [`v9.0.1`](https://github.com/pytest-dev/pytest/releases/tag/9.0.1) [Compare Source](pytest-dev/pytest@9.0.0...9.0.1) ### pytest 9.0.1 (2025-11-12) #### Bug fixes - [#13895](pytest-dev/pytest#13895): Restore support for skipping tests via `raise unittest.SkipTest`. - [#13896](pytest-dev/pytest#13896): The terminal progress plugin added in pytest 9.0 is now automatically disabled when iTerm2 is detected, it generated desktop notifications instead of the desired functionality. - [#13904](pytest-dev/pytest#13904): Fixed the TOML type of the verbosity settings in the API reference from number to string. - [#13910](pytest-dev/pytest#13910): Fixed UserWarning: Do not expect file\_or\_dir on some earlier Python 3.12 and 3.13 point versions. #### Packaging updates and notes for downstreams - [#13933](pytest-dev/pytest#13933): The tox configuration has been adjusted to make sure the desired version string can be passed into its `package_env` through the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST` environment variable as a part of the release process -- by `webknjaz`. #### Contributor-facing changes - [#13891](pytest-dev/pytest#13891), [#13942](pytest-dev/pytest#13942): The CI/CD part of the release automation is now capable of creating GitHub Releases without having a Git checkout on disk -- by `bluetech` and `webknjaz`. - [#13933](pytest-dev/pytest#13933): The tox configuration has been adjusted to make sure the desired version string can be passed into its `package_env` through the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST` environment variable as a part of the release process -- by `webknjaz`. ### [`v9.0.0`](https://github.com/pytest-dev/pytest/releases/tag/9.0.0) [Compare Source](pytest-dev/pytest@8.4.2...9.0.0) ### pytest 9.0.0 (2025-11-05) #### New features - [#1367](pytest-dev/pytest#1367): **Support for subtests** has been added. `subtests <subtests>` are an alternative to parametrization, useful in situations where the parametrization values are not all known at collection time. Example: ```python def contains_docstring(p: Path) -> bool: """Return True if the given Python file contains a top-level docstring.""" ... def test_py_files_contain_docstring(subtests: pytest.Subtests) -> None: for path in Path.cwd().glob("*.py"): with subtests.test(path=str(path)): assert contains_docstring(path) ``` Each assert failure or error is caught by the context manager and reported individually, giving a clear picture of all files that are missing a docstring. In addition, `unittest.TestCase.subTest` is now also supported. This feature was originally implemented as a separate plugin in [pytest-subtests](https://github.com/pytest-dev/pytest-subtests), but since then has been merged into the core. > \[!NOTE] > This feature is experimental and will likely evolve in future releases. By that we mean that we might change how subtests are reported on failure, but the functionality and how to use it are stable. - [#13743](pytest-dev/pytest#13743): Added support for **native TOML configuration files**. While pytest, since version 6, supports configuration in `pyproject.toml` files under `[tool.pytest.ini_options]`, it does so in an "INI compatibility mode", where all configuration values are treated as strings or list of strings. Now, pytest supports the native TOML data model. In `pyproject.toml`, the native TOML configuration is under the `[tool.pytest]` table. ```toml # pyproject.toml [tool.pytest] minversion = "9.0" addopts = ["-ra", "-q"] testpaths = [ "tests", "integration", ] ``` The `[tool.pytest.ini_options]` table remains supported, but both tables cannot be used at the same time. If you prefer to use a separate configuration file, or don't use `pyproject.toml`, you can use `pytest.toml` or `.pytest.toml`: ```toml # pytest.toml or .pytest.toml [pytest] minversion = "9.0" addopts = ["-ra", "-q"] testpaths = [ "tests", "integration", ] ``` The documentation now (sometimes) shows configuration snippets in both TOML and INI formats, in a tabbed interface. See `config file formats` for full details. - [#13823](pytest-dev/pytest#13823): Added a **"strict mode"** enabled by the `strict` configuration option. When set to `true`, the `strict` option currently enables - `strict_config` - `strict_markers` - `strict_parametrization_ids` - `strict_xfail` The individual strictness options can be explicitly set to override the global `strict` setting. The previously-deprecated `--strict` command-line flag now enables strict mode. If pytest adds new strictness options in the future, they will also be enabled in strict mode. Therefore, you should only enable strict mode if you use a pinned/locked version of pytest, or if you want to proactively adopt new strictness options as they are added. See `strict mode` for more details. - [#13737](pytest-dev/pytest#13737): Added the `strict_parametrization_ids` configuration option. When set, pytest emits an error if it detects non-unique parameter set IDs, rather than automatically making the IDs unique by adding 0, 1, ... to them. This can be particularly useful for catching unintended duplicates. - [#13072](pytest-dev/pytest#13072): Added support for displaying test session **progress in the terminal tab** using the [OSC 9;4;](https://conemu.github.io/en/AnsiEscapeCodes.html#ConEmu_specific_OSC) ANSI sequence. When pytest runs in a supported terminal emulator like ConEmu, Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty, you'll see the progress in the terminal tab or window, allowing you to monitor pytest's progress at a glance. This feature is automatically enabled when running in a TTY. It is implemented as an internal plugin. If needed, it can be disabled as follows: - On a user level, using `-p no:terminalprogress` on the command line or via an environment variable `PYTEST_ADDOPTS='-p no:terminalprogress'`. - On a project configuration level, using `addopts = "-p no:terminalprogress"`. - [#478](pytest-dev/pytest#478): Support PEP420 (implicit namespace packages) as --pyargs target when `consider_namespace_packages` is true in the config. Previously, this option only impacted package imports, now it also impacts tests discovery. - [#13678](pytest-dev/pytest#13678): Added a new `faulthandler_exit_on_timeout` configuration option set to "false" by default to let faulthandler interrupt the pytest process after a timeout in case of deadlock. Previously, a faulthandler timeout would only dump the traceback of all threads to stderr, but would not interrupt the pytest process. \-- by `ogrisel`. - [#13829](pytest-dev/pytest#13829): Added support for configuration option aliases via the `aliases` parameter in `Parser.addini() <pytest.Parser.addini>`. Plugins can now register alternative names for configuration options, allowing for more flexibility in configuration naming and supporting backward compatibility when renaming options. The canonical name always takes precedence if both the canonical name and an alias are specified in the configuration file. #### Improvements in existing functionality - [#13330](pytest-dev/pytest#13330): Having pytest configuration spread over more than one file (for example having both a `pytest.ini` file and `pyproject.toml` with a `[tool.pytest.ini_options]` table) will now print a warning to make it clearer to the user that only one of them is actually used. \-- by `sgaist` - [#13574](pytest-dev/pytest#13574): The single argument `--version` no longer loads the entire plugin infrastructure, making it faster and more reliable when displaying only the pytest version. Passing `--version` twice (e.g., `pytest --version --version`) retains the original behavior, showing both the pytest version and plugin information. > \[!NOTE] > Since `--version` is now processed early, it only takes effect when passed directly via the command line. It will not work if set through other mechanisms, such as `PYTEST_ADDOPTS` or `addopts`. - [#13823](pytest-dev/pytest#13823): Added `strict_xfail` as an alias to the `xfail_strict` option, `strict_config` as an alias to the `--strict-config` flag, and `strict_markers` as an alias to the `--strict-markers` flag. This makes all strictness options consistently have configuration options with the prefix `strict_`. - [#13700](pytest-dev/pytest#13700): --junitxml no longer prints the generated xml file summary at the end of the pytest session when --quiet is given. - [#13732](pytest-dev/pytest#13732): Previously, when filtering warnings, pytest would fail if the filter referenced a class that could not be imported. Now, this only outputs a message indicating the problem. - [#13859](pytest-dev/pytest#13859): Clarify the error message for pytest.raises() when a regex match fails. - [#13861](pytest-dev/pytest#13861): Better sentence structure in a test's expected error message. Previously, the error message would be "expected exception must be \<expected>, but got \<actual>". Now, it is "Expected \<expected>, but got \<actual>". #### Removals and backward incompatible breaking changes - [#12083](pytest-dev/pytest#12083): Fixed a bug where an invocation such as pytest a/ a/b would cause only tests from a/b to run, and not other tests under a/. The fix entails a few breaking changes to how such overlapping arguments and duplicates are handled: 1. pytest a/b a/ or pytest a/ a/b are equivalent to pytest a; if an argument overlaps another arguments, only the prefix remains. 2. pytest x.py x.py is equivalent to pytest x.py; previously such an invocation was taken as an explicit request to run the tests from the file twice. If you rely on these behaviors, consider using `--keep-duplicates <duplicate-paths>`, which retains its existing behavior (including the bug). - [#13719](pytest-dev/pytest#13719): Support for Python 3.9 is dropped following its end of life. - [#13766](pytest-dev/pytest#13766): Previously, pytest would assume it was running in a CI/CD environment if either of the environment variables $CI or $BUILD\_NUMBER was defined; now, CI mode is only activated if at least one of those variables is defined and set to a *non-empty* value. - [#13779](pytest-dev/pytest#13779): **PytestRemovedIn9Warning deprecation warnings are now errors by default.** Following our plan to remove deprecated features with as little disruption as possible, all warnings of type `PytestRemovedIn9Warning` now generate errors instead of warning messages by default. **The affected features will be effectively removed in pytest 9.1**, so please consult the `deprecations` section in the docs for directions on how to update existing code. In the pytest `9.0.X` series, it is possible to change the errors back into warnings as a stopgap measure by adding this to your `pytest.ini` file: ```ini [pytest] filterwarnings = ignore::pytest.PytestRemovedIn9Warning ``` But this will stop working when pytest `9.1` is released. **If you have concerns** about the removal of a specific feature, please add a comment to `13779`. #### Deprecations (removal in next major release) - [#13807](pytest-dev/pytest#13807): `monkeypatch.syspath_prepend() <pytest.MonkeyPatch.syspath_prepend>` now issues a deprecation warning when the prepended path contains legacy namespace packages (those using `pkg_resources.declare_namespace()`). Users should migrate to native namespace packages (`420`). See `monkeypatch-fixup-namespace-packages` for details. #### Bug fixes - [#13445](pytest-dev/pytest#13445): Made the type annotations of `pytest.skip` and friends more spec-complaint to have them work across more type checkers. - [#13537](pytest-dev/pytest#13537): Fixed a bug in which `ExceptionGroup` with only `Skipped` exceptions in teardown was not handled correctly and showed as error. - [#13598](pytest-dev/pytest#13598): Fixed possible collection confusion on Windows when short paths and symlinks are involved. - [#13716](pytest-dev/pytest#13716): Fixed a bug where a nonsensical invocation like `pytest x.py[a]` (a file cannot be parametrized) was silently treated as `pytest x.py`. This is now a usage error. - [#13722](pytest-dev/pytest#13722): Fixed a misleading assertion failure message when using `pytest.approx` on mappings with differing lengths. - [#13773](pytest-dev/pytest#13773): Fixed the static fixture closure calculation to properly consider transitive dependencies requested by overridden fixtures. - [#13816](pytest-dev/pytest#13816): Fixed `pytest.approx` which now returns a clearer error message when comparing mappings with different keys. - [#13849](pytest-dev/pytest#13849): Hidden `.pytest.ini` files are now picked up as the config file even if empty. This was an inconsistency with non-hidden `pytest.ini`. - [#13865](pytest-dev/pytest#13865): Fixed --show-capture with --tb=line. - [#13522](pytest-dev/pytest#13522): Fixed `pytester` in subprocess mode ignored all :attr\`pytester.plugins \<pytest.Pytester.plugins>\` except the first. Fixed `pytester` in subprocess mode silently ignored non-str `pytester.plugins <pytest.Pytester.plugins>`. Now it errors instead. If you are affected by this, specify the plugin by name, or switch the affected tests to use `pytester.runpytest_inprocess <pytest.Pytester.runpytest_inprocess>` explicitly instead. #### Packaging updates and notes for downstreams - [#13791](pytest-dev/pytest#13791): Minimum requirements on `iniconfig` and `packaging` were bumped to `1.0.1` and `22.0.0`, respectively. #### Contributor-facing changes - [#12244](pytest-dev/pytest#12244): Fixed self-test failures when TERM=dumb. - [#12474](pytest-dev/pytest#12474): Added scheduled GitHub Action Workflow to run Sphinx linkchecks in repo documentation. - [#13621](pytest-dev/pytest#13621): pytest's own testsuite now handles the `lsof` command hanging (e.g. due to unreachable network filesystems), with the affected selftests being skipped after 10 seconds. - [#13638](pytest-dev/pytest#13638): Fixed deprecated `gh pr new` command in `scripts/prepare-release-pr.py`. The script now uses `gh pr create` which is compatible with GitHub CLI v2.0+. - [#13695](pytest-dev/pytest#13695): Flush stdout and stderr in Pytester.run to avoid truncated outputs in test\_faulthandler.py::test\_timeout on CI -- by `ogrisel`. - [#13771](pytest-dev/pytest#13771): Skip test\_do\_not\_collect\_symlink\_siblings on Windows environments without symlink support to avoid false negatives. - [#13841](pytest-dev/pytest#13841): `tox>=4` is now required when contributing to pytest. - [#13625](pytest-dev/pytest#13625): Added missing docstrings to `pytest_addoption()`, `pytest_configure()`, and `cacheshow()` functions in `cacheprovider.py`. #### Miscellaneous internal changes - [#13830](pytest-dev/pytest#13830): Configuration overrides (`-o`/`--override-ini`) are now processed during startup rather than during `config.getini() <pytest.Config.getini>`. </details> --- - [ ] If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  See merge request swiss-armed-forces/cyber-command/cea/loom!285 Co-authored-by: Loom MR Pipeline Trigger <group_103951964_bot_9504bb8dead6d4e406ad817a607f24be@noreply.gitlab.com> Co-authored-by: shrewd-laidback palace <shrewd-laidback-palace-736-c41-2c1-e464fc974@swiss-armed-forces-open-source.ch>

chore(deps): update pytest (major) This MR contains the following updates: | Package | Type | Update | Change | OpenSSF | |---|---|---|---|---| | [pytest](https://github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html)) | test | major | `^8.2.0` → `^9.0.0` | [![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/pytest-dev/pytest/badge)](https://securityscorecards.dev/viewer/?uri=github.com/pytest-dev/pytest) | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.0.2`](https://github.com/pytest-dev/pytest/releases/tag/9.0.2) [Compare Source](pytest-dev/pytest@9.0.1...9.0.2) ### pytest 9.0.2 (2025-12-06) #### Bug fixes - [#13896](pytest-dev/pytest#13896): The terminal progress feature added in pytest 9.0.0 has been disabled by default, except on Windows, due to compatibility issues with some terminal emulators. You may enable it again by passing `-p terminalprogress`. We may enable it by default again once compatibility improves in the future. Additionally, when the environment variable `TERM` is `dumb`, the escape codes are no longer emitted, even if the plugin is enabled. - [#13904](pytest-dev/pytest#13904): Fixed the TOML type of the `tmp_path_retention_count` settings in the API reference from number to string. - [#13946](pytest-dev/pytest#13946): The private `config.inicfg` attribute was changed in a breaking manner in pytest 9.0.0. Due to its usage in the ecosystem, it is now restored to working order using a compatibility shim. It will be deprecated in pytest 9.1 and removed in pytest 10. - [#13965](pytest-dev/pytest#13965): Fixed quadratic-time behavior when handling `unittest` subtests in Python 3.10. #### Improved documentation - [#4492](pytest-dev/pytest#4492): The API Reference now contains cross-reference-able documentation of `pytest's command-line flags <command-line-flags>`. ### [`v9.0.1`](https://github.com/pytest-dev/pytest/releases/tag/9.0.1) [Compare Source](pytest-dev/pytest@9.0.0...9.0.1) ### pytest 9.0.1 (2025-11-12) #### Bug fixes - [#13895](pytest-dev/pytest#13895): Restore support for skipping tests via `raise unittest.SkipTest`. - [#13896](pytest-dev/pytest#13896): The terminal progress plugin added in pytest 9.0 is now automatically disabled when iTerm2 is detected, it generated desktop notifications instead of the desired functionality. - [#13904](pytest-dev/pytest#13904): Fixed the TOML type of the verbosity settings in the API reference from number to string. - [#13910](pytest-dev/pytest#13910): Fixed UserWarning: Do not expect file\_or\_dir on some earlier Python 3.12 and 3.13 point versions. #### Packaging updates and notes for downstreams - [#13933](pytest-dev/pytest#13933): The tox configuration has been adjusted to make sure the desired version string can be passed into its `package_env` through the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST` environment variable as a part of the release process -- by `webknjaz`. #### Contributor-facing changes - [#13891](pytest-dev/pytest#13891), [#13942](pytest-dev/pytest#13942): The CI/CD part of the release automation is now capable of creating GitHub Releases without having a Git checkout on disk -- by `bluetech` and `webknjaz`. - [#13933](pytest-dev/pytest#13933): The tox configuration has been adjusted to make sure the desired version string can be passed into its `package_env` through the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST` environment variable as a part of the release process -- by `webknjaz`. ### [`v9.0.0`](https://github.com/pytest-dev/pytest/releases/tag/9.0.0) [Compare Source](pytest-dev/pytest@8.4.2...9.0.0) ### pytest 9.0.0 (2025-11-05) #### New features - [#1367](pytest-dev/pytest#1367): **Support for subtests** has been added. `subtests <subtests>` are an alternative to parametrization, useful in situations where the parametrization values are not all known at collection time. Example: ```python def contains_docstring(p: Path) -> bool: """Return True if the given Python file contains a top-level docstring.""" ... def test_py_files_contain_docstring(subtests: pytest.Subtests) -> None: for path in Path.cwd().glob("*.py"): with subtests.test(path=str(path)): assert contains_docstring(path) ``` Each assert failure or error is caught by the context manager and reported individually, giving a clear picture of all files that are missing a docstring. In addition, `unittest.TestCase.subTest` is now also supported. This feature was originally implemented as a separate plugin in [pytest-subtests](https://github.com/pytest-dev/pytest-subtests), but since then has been merged into the core. > \[!NOTE] > This feature is experimental and will likely evolve in future releases. By that we mean that we might change how subtests are reported on failure, but the functionality and how to use it are stable. - [#13743](pytest-dev/pytest#13743): Added support for **native TOML configuration files**. While pytest, since version 6, supports configuration in `pyproject.toml` files under `[tool.pytest.ini_options]`, it does so in an "INI compatibility mode", where all configuration values are treated as strings or list of strings. Now, pytest supports the native TOML data model. In `pyproject.toml`, the native TOML configuration is under the `[tool.pytest]` table. ```toml # pyproject.toml [tool.pytest] minversion = "9.0" addopts = ["-ra", "-q"] testpaths = [ "tests", "integration", ] ``` The `[tool.pytest.ini_options]` table remains supported, but both tables cannot be used at the same time. If you prefer to use a separate configuration file, or don't use `pyproject.toml`, you can use `pytest.toml` or `.pytest.toml`: ```toml # pytest.toml or .pytest.toml [pytest] minversion = "9.0" addopts = ["-ra", "-q"] testpaths = [ "tests", "integration", ] ``` The documentation now (sometimes) shows configuration snippets in both TOML and INI formats, in a tabbed interface. See `config file formats` for full details. - [#13823](pytest-dev/pytest#13823): Added a **"strict mode"** enabled by the `strict` configuration option. When set to `true`, the `strict` option currently enables - `strict_config` - `strict_markers` - `strict_parametrization_ids` - `strict_xfail` The individual strictness options can be explicitly set to override the global `strict` setting. The previously-deprecated `--strict` command-line flag now enables strict mode. If pytest adds new strictness options in the future, they will also be enabled in strict mode. Therefore, you should only enable strict mode if you use a pinned/locked version of pytest, or if you want to proactively adopt new strictness options as they are added. See `strict mode` for more details. - [#13737](pytest-dev/pytest#13737): Added the `strict_parametrization_ids` configuration option. When set, pytest emits an error if it detects non-unique parameter set IDs, rather than automatically making the IDs unique by adding 0, 1, ... to them. This can be particularly useful for catching unintended duplicates. - [#13072](pytest-dev/pytest#13072): Added support for displaying test session **progress in the terminal tab** using the [OSC 9;4;](https://conemu.github.io/en/AnsiEscapeCodes.html#ConEmu_specific_OSC) ANSI sequence. When pytest runs in a supported terminal emulator like ConEmu, Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty, you'll see the progress in the terminal tab or window, allowing you to monitor pytest's progress at a glance. This feature is automatically enabled when running in a TTY. It is implemented as an internal plugin. If needed, it can be disabled as follows: - On a user level, using `-p no:terminalprogress` on the command line or via an environment variable `PYTEST_ADDOPTS='-p no:terminalprogress'`. - On a project configuration level, using `addopts = "-p no:terminalprogress"`. - [#478](pytest-dev/pytest#478): Support PEP420 (implicit namespace packages) as --pyargs target when `consider_namespace_packages` is true in the config. Previously, this option only impacted package imports, now it also impacts tests discovery. - [#13678](pytest-dev/pytest#13678): Added a new `faulthandler_exit_on_timeout` configuration option set to "false" by default to let faulthandler interrupt the pytest process after a timeout in case of deadlock. Previously, a faulthandler timeout would only dump the traceback of all threads to stderr, but would not interrupt the pytest process. \-- by `ogrisel`. - [#13829](pytest-dev/pytest#13829): Added support for configuration option aliases via the `aliases` parameter in `Parser.addini() <pytest.Parser.addini>`. Plugins can now register alternative names for configuration options, allowing for more flexibility in configuration naming and supporting backward compatibility when renaming options. The canonical name always takes precedence if both the canonical name and an alias are specified in the configuration file. #### Improvements in existing functionality - [#13330](pytest-dev/pytest#13330): Having pytest configuration spread over more than one file (for example having both a `pytest.ini` file and `pyproject.toml` with a `[tool.pytest.ini_options]` table) will now print a warning to make it clearer to the user that only one of them is actually used. \-- by `sgaist` - [#13574](pytest-dev/pytest#13574): The single argument `--version` no longer loads the entire plugin infrastructure, making it faster and more reliable when displaying only the pytest version. Passing `--version` twice (e.g., `pytest --version --version`) retains the original behavior, showing both the pytest version and plugin information. > \[!NOTE] > Since `--version` is now processed early, it only takes effect when passed directly via the command line. It will not work if set through other mechanisms, such as `PYTEST_ADDOPTS` or `addopts`. - [#13823](pytest-dev/pytest#13823): Added `strict_xfail` as an alias to the `xfail_strict` option, `strict_config` as an alias to the `--strict-config` flag, and `strict_markers` as an alias to the `--strict-markers` flag. This makes all strictness options consistently have configuration options with the prefix `strict_`. - [#13700](pytest-dev/pytest#13700): --junitxml no longer prints the generated xml file summary at the end of the pytest session when --quiet is given. - [#13732](pytest-dev/pytest#13732): Previously, when filtering warnings, pytest would fail if the filter referenced a class that could not be imported. Now, this only outputs a message indicating the problem. - [#13859](pytest-dev/pytest#13859): Clarify the error message for pytest.raises() when a regex match fails. - [#13861](pytest-dev/pytest#13861): Better sentence structure in a test's expected error message. Previously, the error message would be "expected exception must be \<expected>, but got \<actual>". Now, it is "Expected \<expected>, but got \<actual>". #### Removals and backward incompatible breaking changes - [#12083](pytest-dev/pytest#12083): Fixed a bug where an invocation such as pytest a/ a/b would cause only tests from a/b to run, and not other tests under a/. The fix entails a few breaking changes to how such overlapping arguments and duplicates are handled: 1. pytest a/b a/ or pytest a/ a/b are equivalent to pytest a; if an argument overlaps another arguments, only the prefix remains. 2. pytest x.py x.py is equivalent to pytest x.py; previously such an invocation was taken as an explicit request to run the tests from the file twice. If you rely on these behaviors, consider using `--keep-duplicates <duplicate-paths>`, which retains its existing behavior (including the bug). - [#13719](pytest-dev/pytest#13719): Support for Python 3.9 is dropped following its end of life. - [#13766](pytest-dev/pytest#13766): Previously, pytest would assume it was running in a CI/CD environment if either of the environment variables $CI or $BUILD\_NUMBER was defined; now, CI mode is only activated if at least one of those variables is defined and set to a *non-empty* value. - [#13779](pytest-dev/pytest#13779): **PytestRemovedIn9Warning deprecation warnings are now errors by default.** Following our plan to remove deprecated features with as little disruption as possible, all warnings of type `PytestRemovedIn9Warning` now generate errors instead of warning messages by default. **The affected features will be effectively removed in pytest 9.1**, so please consult the `deprecations` section in the docs for directions on how to update existing code. In the pytest `9.0.X` series, it is possible to change the errors back into warnings as a stopgap measure by adding this to your `pytest.ini` file: ```ini [pytest] filterwarnings = ignore::pytest.PytestRemovedIn9Warning ``` But this will stop working when pytest `9.1` is released. **If you have concerns** about the removal of a specific feature, please add a comment to `13779`. #### Deprecations (removal in next major release) - [#13807](pytest-dev/pytest#13807): `monkeypatch.syspath_prepend() <pytest.MonkeyPatch.syspath_prepend>` now issues a deprecation warning when the prepended path contains legacy namespace packages (those using `pkg_resources.declare_namespace()`). Users should migrate to native namespace packages (`420`). See `monkeypatch-fixup-namespace-packages` for details. #### Bug fixes - [#13445](pytest-dev/pytest#13445): Made the type annotations of `pytest.skip` and friends more spec-complaint to have them work across more type checkers. - [#13537](pytest-dev/pytest#13537): Fixed a bug in which `ExceptionGroup` with only `Skipped` exceptions in teardown was not handled correctly and showed as error. - [#13598](pytest-dev/pytest#13598): Fixed possible collection confusion on Windows when short paths and symlinks are involved. - [#13716](pytest-dev/pytest#13716): Fixed a bug where a nonsensical invocation like `pytest x.py[a]` (a file cannot be parametrized) was silently treated as `pytest x.py`. This is now a usage error. - [#13722](pytest-dev/pytest#13722): Fixed a misleading assertion failure message when using `pytest.approx` on mappings with differing lengths. - [#13773](pytest-dev/pytest#13773): Fixed the static fixture closure calculation to properly consider transitive dependencies requested by overridden fixtures. - [#13816](pytest-dev/pytest#13816): Fixed `pytest.approx` which now returns a clearer error message when comparing mappings with different keys. - [#13849](pytest-dev/pytest#13849): Hidden `.pytest.ini` files are now picked up as the config file even if empty. This was an inconsistency with non-hidden `pytest.ini`. - [#13865](pytest-dev/pytest#13865): Fixed --show-capture with --tb=line. - [#13522](pytest-dev/pytest#13522): Fixed `pytester` in subprocess mode ignored all :attr\`pytester.plugins \<pytest.Pytester.plugins>\` except the first. Fixed `pytester` in subprocess mode silently ignored non-str `pytester.plugins <pytest.Pytester.plugins>`. Now it errors instead. If you are affected by this, specify the plugin by name, or switch the affected tests to use `pytester.runpytest_inprocess <pytest.Pytester.runpytest_inprocess>` explicitly instead. #### Packaging updates and notes for downstreams - [#13791](pytest-dev/pytest#13791): Minimum requirements on `iniconfig` and `packaging` were bumped to `1.0.1` and `22.0.0`, respectively. #### Contributor-facing changes - [#12244](pytest-dev/pytest#12244): Fixed self-test failures when TERM=dumb. - [#12474](pytest-dev/pytest#12474): Added scheduled GitHub Action Workflow to run Sphinx linkchecks in repo documentation. - [#13621](pytest-dev/pytest#13621): pytest's own testsuite now handles the `lsof` command hanging (e.g. due to unreachable network filesystems), with the affected selftests being skipped after 10 seconds. - [#13638](pytest-dev/pytest#13638): Fixed deprecated `gh pr new` command in `scripts/prepare-release-pr.py`. The script now uses `gh pr create` which is compatible with GitHub CLI v2.0+. - [#13695](pytest-dev/pytest#13695): Flush stdout and stderr in Pytester.run to avoid truncated outputs in test\_faulthandler.py::test\_timeout on CI -- by `ogrisel`. - [#13771](pytest-dev/pytest#13771): Skip test\_do\_not\_collect\_symlink\_siblings on Windows environments without symlink support to avoid false negatives. - [#13841](pytest-dev/pytest#13841): `tox>=4` is now required when contributing to pytest. - [#13625](pytest-dev/pytest#13625): Added missing docstrings to `pytest_addoption()`, `pytest_configure()`, and `cacheshow()` functions in `cacheprovider.py`. #### Miscellaneous internal changes - [#13830](pytest-dev/pytest#13830): Configuration overrides (`-o`/`--override-ini`) are now processed during startup rather than during `config.getini() <pytest.Config.getini>`. </details> --- - [ ] If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  See merge request swiss-armed-forces/cyber-command/cea/loom!285 Co-authored-by: Loom MR Pipeline Trigger <group_103951964_bot_9504bb8dead6d4e406ad817a607f24be@noreply.gitlab.com> Co-authored-by: open-source Pipeline <group_90701827_bot_ed04ae348bc5f40af9966fb8b6867e99@noreply.gitlab.com>

webknjaz added 2 commits November 11, 2025 19:28

📝 Add a change note for PR pytest-dev#13933

7df3b1b

psf-chronographer bot added the bot:chronographer:provided (automation) changelog entry is part of PR label Nov 11, 2025

webknjaz requested review from bluetech, Copilot and nicoddemus November 11, 2025 18:44

Copilot started reviewing on behalf of webknjaz November 11, 2025 18:45 View session

Copilot finished reviewing on behalf of webknjaz November 11, 2025 18:45

webknjaz commented Nov 11, 2025

View reviewed changes

webknjaz marked this pull request as ready for review November 11, 2025 18:46

Copilot AI reviewed Nov 11, 2025

View reviewed changes

changelog/13933.packaging.rst Show resolved Hide resolved

changelog/13933.contrib.rst Show resolved Hide resolved

bluetech approved these changes Nov 11, 2025

View reviewed changes

bluetech added the backport 9.0.x apply to PRs at any point; backports the changes to the 9.0.x branch label Nov 11, 2025

bluetech reviewed Nov 11, 2025

View reviewed changes

webknjaz mentioned this pull request Nov 11, 2025

Release 9.0.1 #13928

Closed

webknjaz merged commit ce8b8a7 into pytest-dev:main Nov 11, 2025
47 of 68 checks passed

patchback bot pushed a commit that referenced this pull request Nov 11, 2025

Merge pull request #13933 from webknjaz/maintenance/tox-pep517-env-se…

15f93b3

…tuptools-scm-pretend-env-var 📦 Pass desired release to PEP 517 tox env (cherry picked from commit ce8b8a7)

patchback bot mentioned this pull request Nov 11, 2025

[PR #13933/ce8b8a7b backport][9.0.x] 📦 Pass desired release to PEP 517 tox env #13935

Merged

webknjaz added a commit that referenced this pull request Nov 11, 2025

Merge pull request #13935 from pytest-dev/patchback/backports/9.0.x/c…

4bd63a0

…e8b8a7b4b360ac5f3953b8c3b8b59e6bb420f37/pr-13933 [PR #13933/ce8b8a7b backport][9.0.x] 📦 Pass desired release to PEP 517 tox env

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

📦 Pass desired release to PEP 517 tox env#13933

📦 Pass desired release to PEP 517 tox env#13933
webknjaz merged 2 commits intopytest-dev:mainfrom
webknjaz:maintenance/tox-pep517-env-setuptools-scm-pretend-env-var

webknjaz commented Nov 11, 2025

Uh oh!

webknjaz Nov 11, 2025

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Uh oh!

bluetech left a comment

Uh oh!

bluetech Nov 11, 2025

Uh oh!

webknjaz Nov 11, 2025

Uh oh!

webknjaz commented Nov 11, 2025

Uh oh!

webknjaz commented Nov 11, 2025

Uh oh!

webknjaz commented Nov 11, 2025

Uh oh!

webknjaz commented Nov 11, 2025

Uh oh!

Uh oh!

patchback bot commented Nov 11, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

webknjaz commented Nov 11, 2025

Uh oh!

webknjaz Nov 11, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Reviewed Changes

Uh oh!

Uh oh!

Uh oh!

bluetech left a comment

Choose a reason for hiding this comment

Uh oh!

bluetech Nov 11, 2025

Choose a reason for hiding this comment

Uh oh!

webknjaz Nov 11, 2025

Choose a reason for hiding this comment

Uh oh!

webknjaz commented Nov 11, 2025

Uh oh!

webknjaz commented Nov 11, 2025

Uh oh!

webknjaz commented Nov 11, 2025

Uh oh!

webknjaz commented Nov 11, 2025

Uh oh!

Uh oh!

patchback bot commented Nov 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Backport to 9.0.x: 💚 backport PR created

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

patchback bot commented Nov 11, 2025 •

edited

Loading