TOML config opts verbosity_assertions, verbosity_subtests, & verbosity_test_cases no longer accept numeric string values in 9.2.0 #15290

Activity

1. Lpk124 commented on Oct 29, 2026

   

   Lpk124

   on Oct 29, 2026

   More actions

   I reproduced the 9.2.0 regression and opened #15294 with focused TOML numeric-string coverage for the three verbosity options. The compatibility path is limited to the built-in verbosity settings; generic plugin int | str and int | Literal[...] unions remain strict.
2. bashonly commented on Oct 29, 2026

   

   bashonly

   on Oct 29, 2026

   Last edited by bashonly

   Author

   More actions

   Edit: using tool.pytest.ini_options instead of tool.pytest in pyproject.toml is a viable workaround. Thanks @yardenac
3. yardenac commented on Oct 29, 2026

   

   yardenac

   on Oct 29, 2026

   Last edited by yardenac

   More actions

   3. This is a frustrating regression since my project's config only works with pytest<9.2.0 as-is, and if I adjust the config for latest pytest then it will only work with pytest>=9.2.0. I can't seem to find any workaround that will preserve my settings and satisfy both <9.2.0 and 9.2.0.

   it seems this was intentional:

   this ... removes a intentional tightening of the behavior

   this pr accepts the old way again, but with a deprecation warning. either way, the only workaround will be to check pytest's version first, or to require a certain version

   EDIT: ... or to use ini_options
4. bashonly

   added a commit that references this issue on Oct 29, 2026

   [misc] Use `ini_options` table for pytest config (#17952)

   ...

   0b8f725
5. RonnyPfannschmidt

   closed this as completedin #15296on Nov 4, 2026
6. 2badagoldman

   added a commit that references this issue on Nov 4, 2026

   Accept numeric strings for verbosity options in native TOML again

   ...

   This issue will close once commit 6ed587d is merged into the 'main' branch.

   6ed587d