Skip to content

doc: fix toml type of verbosity options in API reference #13906

New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 10, 2025
+4 −3
Merged

doc: fix toml type of verbosity options in API reference #13906

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelog/13904.bugfix.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Fixed the TOML type of the verbosity settings in the API reference from number to string.
6 changes: 3 additions & 3 deletions doc/en/reference/reference.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2596,7 +2596,7 @@ passed multiple times. The expected format is ``name=value``. For example::
.. code-block:: toml

[pytest]
verbosity_assertions = 2
verbosity_assertions = "2"

.. tab:: ini

Expand All @@ -2618,7 +2618,7 @@ passed multiple times. The expected format is ``name=value``. For example::
.. code-block:: toml

[pytest]
verbosity_subtests = 1
verbosity_subtests = "1"

.. tab:: ini

Expand All @@ -2645,7 +2645,7 @@ passed multiple times. The expected format is ``name=value``. For example::
.. code-block:: toml

[pytest]
verbosity_test_cases = 2
verbosity_test_cases = "2"

.. tab:: ini

Expand Down