pytest 8.4.0__tar.gz → 8.4.2__tar.gz

{pytest-8.4.0 → pytest-8.4.2}/.github/workflows/deploy.yml

@@ -109,8 +109,8 @@ jobs:
         tox -e generate-gh-release-notes -- "$VERSION" scripts/latest-release-notes.md
 
     - name: Publish GitHub Release
-      uses: softprops/action-gh-release@da05d552573ad5aba039eaac05058a918a7bf631
-      with:
-        body_path: scripts/latest-release-notes.md
-        files: dist/*
-        tag_name: ${{ github.event.inputs.version }}
+      env:
+        VERSION: ${{ github.event.inputs.version }}
+        GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      run: |
+        gh release create --notes-file scripts/latest-release-notes.md --verify-tag "$VERSION" dist/*

{pytest-8.4.0 → pytest-8.4.2}/.github/workflows/test.yml

@@ -54,7 +54,9 @@ jobs:
       fail-fast: false
       matrix:
         name: [
-          "windows-py39-unittestextras",
+          "windows-py39-unittest-asynctest",
+          "windows-py39-unittest-twisted24",
+          "windows-py39-unittest-twisted25",
           "windows-py39-pluggy",
           "windows-py39-xdist",
           "windows-py310",
@@ -63,6 +65,9 @@ jobs:
           "windows-py313",
           "windows-py314",
 
+          "ubuntu-py39-unittest-asynctest",
+          "ubuntu-py39-unittest-twisted24",
+          "ubuntu-py39-unittest-twisted25",
           "ubuntu-py39-lsof-numpy-pexpect",
           "ubuntu-py39-pluggy",
           "ubuntu-py39-freeze",
@@ -85,10 +90,23 @@ jobs:
         ]
 
         include:
-          - name: "windows-py39-unittestextras"
+          # Use separate jobs for different unittest flavors (twisted, asynctest) to ensure proper coverage.
+          - name: "windows-py39-unittest-asynctest"
             python: "3.9"
             os: windows-latest
-            tox_env: "py39-unittestextras"
+            tox_env: "py39-asynctest"
+            use_coverage: true
+
+          - name: "windows-py39-unittest-twisted24"
+            python: "3.9"
+            os: windows-latest
+            tox_env: "py39-twisted24"
+            use_coverage: true
+
+          - name: "windows-py39-unittest-twisted25"
+            python: "3.9"
+            os: windows-latest
+            tox_env: "py39-twisted25"
             use_coverage: true
 
           - name: "windows-py39-pluggy"
@@ -126,6 +144,25 @@ jobs:
             os: windows-latest
             tox_env: "py314"
 
+          # Use separate jobs for different unittest flavors (twisted, asynctest) to ensure proper coverage.
+          - name: "ubuntu-py39-unittest-asynctest"
+            python: "3.9"
+            os: ubuntu-latest
+            tox_env: "py39-asynctest"
+            use_coverage: true
+
+          - name: "ubuntu-py39-unittest-twisted24"
+            python: "3.9"
+            os: ubuntu-latest
+            tox_env: "py39-twisted24"
+            use_coverage: true
+
+          - name: "ubuntu-py39-unittest-twisted25"
+            python: "3.9"
+            os: ubuntu-latest
+            tox_env: "py39-twisted25"
+            use_coverage: true
+
           - name: "ubuntu-py39-lsof-numpy-pexpect"
             python: "3.9"
             os: ubuntu-latest

{pytest-8.4.0 → pytest-8.4.2}/AUTHORS

@@ -261,6 +261,7 @@ Leonardus Chen
 Lev Maximov
 Levon Saldamli
 Lewis Cowles
+Liam DeVoe
 Llandy Riveron Del Risco
 Loic Esteve
 lovetheguitar

{pytest-8.4.0/src/pytest.egg-info → pytest-8.4.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pytest
-Version: 8.4.0
+Version: 8.4.2
 Summary: pytest: simple powerful testing with Python
 Author: Holger Krekel, Bruno Oliveira, Ronny Pfannschmidt, Floris Bruynooghe, Brianna Laugher, Florian Bruhin, Others (See AUTHORS)
 License: MIT

{pytest-8.4.0 → pytest-8.4.2}/RELEASING.rst

@@ -168,7 +168,6 @@ Both automatic and manual processes described above follow the same steps from t
 
    To the following mailing lists:
 
-   * pytest-dev@python.org (all releases)
    * python-announce-list@python.org (all releases)
    * testing-in-python@lists.idyll.org (only major/minor releases)
 

{pytest-8.4.0 → pytest-8.4.2}/doc/en/announce/index.rst

@@ -6,6 +6,8 @@ Release announcements
    :maxdepth: 2
 
 
+   release-8.4.2
+   release-8.4.1
    release-8.4.0
    release-8.3.5
    release-8.3.4

pytest-8.4.2/doc/en/announce/release-8.4.1.rst

@@ -0,0 +1,21 @@
+pytest-8.4.1
+=======================================
+
+pytest 8.4.1 has just been released to PyPI.
+
+This is a bug-fix release, being a drop-in replacement.
+
+The full changelog is available at https://docs.pytest.org/en/stable/changelog.html.
+
+Thanks to all of the contributors to this release:
+
+* Bruno Oliveira
+* Iwithyou2025
+* John Litborn
+* Martin Fischer
+* Ran Benita
+* SarahPythonista
+
+
+Happy testing,
+The pytest Development Team

pytest-8.4.2/doc/en/announce/release-8.4.2.rst

@@ -0,0 +1,27 @@
+pytest-8.4.2
+=======================================
+
+pytest 8.4.2 has just been released to PyPI.
+
+This is a bug-fix release, being a drop-in replacement.
+
+The full changelog is available at https://docs.pytest.org/en/stable/changelog.html.
+
+Thanks to all of the contributors to this release:
+
+* AD
+* Aditi De
+* Bruno Oliveira
+* Florian Bruhin
+* John Litborn
+* Liam DeVoe
+* Marc Mueller
+* NayeemJohn
+* Olivier Grisel
+* Ran Benita
+* bengartner
+* 🇺🇦 Sviatoslav Sydorenko (Святослав Сидоренко)
+
+
+Happy testing,
+The pytest Development Team

{pytest-8.4.0 → pytest-8.4.2}/doc/en/builtin.rst

@@ -69,7 +69,7 @@ For information about fixtures, see :ref:`fixtures`. To see a complete list of a
 
         .. code-block:: python
 
-            def test_output(capsys):
+            def test_output(capteesys):
                 print("hello")
                 captured = capteesys.readouterr()
                 assert captured.out == "hello\n"
@@ -142,7 +142,7 @@ For information about fixtures, see :ref:`fixtures`. To see a complete list of a
 
         For more details: :ref:`doctest_namespace`.
 
-    pytestconfig [session scope] -- .../_pytest/fixtures.py:1424
+    pytestconfig [session scope] -- .../_pytest/fixtures.py:1425
         Session-scoped fixture that returns the session's :class:`pytest.Config`
         object.
 

{pytest-8.4.0 → pytest-8.4.2}/doc/en/changelog.rst

@@ -31,6 +31,77 @@ with advance notice in the **Deprecations** section of releases.
 
 .. towncrier release notes start
 
+pytest 8.4.2 (2025-09-03)
+=========================
+
+Bug fixes
+---------
+
+- `#13478 <https://github.com/pytest-dev/pytest/issues/13478>`_: Fixed a crash when using :confval:`console_output_style` with ``times`` and a module is skipped.
+
+
+- `#13530 <https://github.com/pytest-dev/pytest/issues/13530>`_: Fixed a crash when using :func:`pytest.approx` and :class:`decimal.Decimal` instances with the :class:`decimal.FloatOperation` trap set.
+
+
+- `#13549 <https://github.com/pytest-dev/pytest/issues/13549>`_: No longer evaluate type annotations in Python ``3.14`` when inspecting function signatures.
+
+  This prevents crashes during module collection when modules do not explicitly use ``from __future__ import annotations`` and import types for annotations within a ``if TYPE_CHECKING:`` block.
+
+
+- `#13559 <https://github.com/pytest-dev/pytest/issues/13559>`_: Added missing `int` and `float` variants to the `Literal` type annotation of the `type` parameter in :meth:`pytest.Parser.addini`.
+
+
+- `#13563 <https://github.com/pytest-dev/pytest/issues/13563>`_: :func:`pytest.approx` now only imports ``numpy`` if NumPy is already in ``sys.modules``. This fixes unconditional import behavior introduced in `8.4.0`.
+
+
+
+Improved documentation
+----------------------
+
+- `#13577 <https://github.com/pytest-dev/pytest/issues/13577>`_: Clarify that ``pytest_generate_tests`` is discovered in test modules/classes; other hooks must be in ``conftest.py`` or plugins.
+
+
+
+Contributor-facing changes
+--------------------------
+
+- `#13480 <https://github.com/pytest-dev/pytest/issues/13480>`_: Self-testing: fixed a few test failures when run with ``-Wdefault`` or a similar override.
+
+
+- `#13547 <https://github.com/pytest-dev/pytest/issues/13547>`_: Self-testing: corrected expected message for ``test_doctest_unexpected_exception`` in Python ``3.14``.
+
+
+- `#13684 <https://github.com/pytest-dev/pytest/issues/13684>`_: Make pytest's own testsuite insensitive to the presence of the ``CI`` environment variable -- by :user:`ogrisel`.
+
+
+pytest 8.4.1 (2025-06-17)
+=========================
+
+Bug fixes
+---------
+
+- `#13461 <https://github.com/pytest-dev/pytest/issues/13461>`_: Corrected ``_pytest.terminal.TerminalReporter.isatty`` to support
+  being called as a method. Before it was just a boolean which could
+  break correct code when using ``-o log_cli=true``).
+
+
+- `#13477 <https://github.com/pytest-dev/pytest/issues/13477>`_: Reintroduced :class:`pytest.PytestReturnNotNoneWarning` which was removed by accident in pytest `8.4`.
+
+  This warning is raised when a test functions returns a value other than ``None``, which is often a mistake made by beginners.
+
+  See :ref:`return-not-none` for more information.
+
+
+- `#13497 <https://github.com/pytest-dev/pytest/issues/13497>`_: Fixed compatibility with ``Twisted 25+``.
+
+
+
+Improved documentation
+----------------------
+
+- `#13492 <https://github.com/pytest-dev/pytest/issues/13492>`_: Fixed outdated warning about ``faulthandler`` not working on Windows.
+
+
 pytest 8.4.0 (2025-06-02)
 =========================
 

{pytest-8.4.0 → pytest-8.4.2}/doc/en/deprecations.rst

@@ -316,46 +316,6 @@ Users expected in this case that the ``usefixtures`` mark would have its intende
 Now pytest will issue a warning when it encounters this problem, and will raise an error in the future versions.
 
 
-Returning non-None value in test functions
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-.. deprecated:: 7.2
-
-A ``pytest.PytestReturnNotNoneWarning`` is now emitted if a test function returns something other than `None`.
-
-This prevents a common mistake among beginners that expect that returning a `bool` would cause a test to pass or fail, for example:
-
-.. code-block:: python
-
-    @pytest.mark.parametrize(
-        ["a", "b", "result"],
-        [
-            [1, 2, 5],
-            [2, 3, 8],
-            [5, 3, 18],
-        ],
-    )
-    def test_foo(a, b, result):
-        return foo(a, b) == result
-
-Given that pytest ignores the return value, this might be surprising that it will never fail.
-
-The proper fix is to change the `return` to an `assert`:
-
-.. code-block:: python
-
-    @pytest.mark.parametrize(
-        ["a", "b", "result"],
-        [
-            [1, 2, 5],
-            [2, 3, 8],
-            [5, 3, 18],
-        ],
-    )
-    def test_foo(a, b, result):
-        assert foo(a, b) == result
-
-
 The ``yield_fixture`` function/decorator
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

{pytest-8.4.0 → pytest-8.4.2}/doc/en/example/parametrize.rst

@@ -162,7 +162,7 @@ objects, they are still using the default pytest representation:
     rootdir: /home/sweet/project
     collected 8 items
 
-    <Dir parametrize.rst-207>
+    <Dir parametrize.rst-209>
       <Module test_time.py>
         <Function test_timedistance_v0[a0-b0-expected0]>
         <Function test_timedistance_v0[a1-b1-expected1]>
@@ -239,7 +239,7 @@ If you just collect tests you'll also nicely see 'advanced' and 'basic' as varia
     rootdir: /home/sweet/project
     collected 4 items
 
-    <Dir parametrize.rst-207>
+    <Dir parametrize.rst-209>
       <Module test_scenarios.py>
         <Class TestSampleWithScenarios>
           <Function test_demo1[basic]>
@@ -318,7 +318,7 @@ Let's first see how it looks like at collection time:
     rootdir: /home/sweet/project
     collected 2 items
 
-    <Dir parametrize.rst-207>
+    <Dir parametrize.rst-209>
       <Module test_backends.py>
         <Function test_db_initialized[d1]>
         <Function test_db_initialized[d2]>
@@ -352,7 +352,7 @@ The first invocation with ``db == "DB1"`` passed while the second with ``db == "
 Indirect parametrization
 ---------------------------------------------------
 
-Using the ``indirect=True`` parameter when parametrizing a test allows to
+Using the ``indirect=True`` parameter when parametrizing a test allows one to
 parametrize a test with a fixture receiving the values before passing them to a
 test:
 

{pytest-8.4.0 → pytest-8.4.2}/doc/en/example/pythoncollection.rst

@@ -152,7 +152,7 @@ The test collection would look like this:
     configfile: pytest.ini
     collected 2 items
 
-    <Dir pythoncollection.rst-208>
+    <Dir pythoncollection.rst-210>
       <Module check_myapp.py>
         <Class CheckMyApp>
           <Function simple_check>
@@ -215,7 +215,7 @@ You can always peek at the collection tree without running tests like this:
     configfile: pytest.ini
     collected 3 items
 
-    <Dir pythoncollection.rst-208>
+    <Dir pythoncollection.rst-210>
       <Dir CWD>
         <Module pythoncollection.py>
           <Function test_function>

{pytest-8.4.0 → pytest-8.4.2}/doc/en/getting-started.rst

@@ -22,7 +22,7 @@ Install ``pytest``
 .. code-block:: bash
 
     $ pytest --version
-    pytest 8.4.0
+    pytest 8.4.2
 
 .. _`simpletest`:
 

{pytest-8.4.0 → pytest-8.4.2}/doc/en/how-to/assert.rst

@@ -476,6 +476,50 @@ the conftest file:
    FAILED test_foocompare.py::test_compare - assert Comparing Foo instances:
    1 failed in 0.12s
 
+.. _`return-not-none`:
+
+Returning non-None value in test functions
+------------------------------------------
+
+A :class:`pytest.PytestReturnNotNoneWarning` is emitted when a test function returns a value other than ``None``.
+
+This helps prevent a common mistake made by beginners who assume that returning a ``bool`` (e.g., ``True`` or ``False``) will determine whether a test passes or fails.
+
+Example:
+
+.. code-block:: python
+
+    @pytest.mark.parametrize(
+        ["a", "b", "result"],
+        [
+            [1, 2, 5],
+            [2, 3, 8],
+            [5, 3, 18],
+        ],
+    )
+    def test_foo(a, b, result):
+        return foo(a, b) == result  # Incorrect usage, do not do this.
+
+Since pytest ignores return values, it might be surprising that the test will never fail based on the returned value.
+
+The correct fix is to replace the ``return`` statement with an ``assert``:
+
+.. code-block:: python
+
+    @pytest.mark.parametrize(
+        ["a", "b", "result"],
+        [
+            [1, 2, 5],
+            [2, 3, 8],
+            [5, 3, 18],
+        ],
+    )
+    def test_foo(a, b, result):
+        assert foo(a, b) == result
+
+
+
+
 .. _assert-details:
 .. _`assert introspection`:
 

{pytest-8.4.0 → pytest-8.4.2}/doc/en/how-to/failures.rst

@@ -112,7 +112,7 @@ on the command-line.
 
 Also the :confval:`faulthandler_timeout=X<faulthandler_timeout>` configuration option can be used
 to dump the traceback of all threads if a test takes longer than ``X``
-seconds to finish (not available on Windows).
+seconds to finish.
 
 .. note::
 

{pytest-8.4.0 → pytest-8.4.2}/doc/en/how-to/fixtures.rst

@@ -1423,7 +1423,7 @@ Running the above tests results in the following test IDs being used:
    rootdir: /home/sweet/project
    collected 12 items
 
-   <Dir fixtures.rst-228>
+   <Dir fixtures.rst-230>
      <Module test_anothersmtp.py>
        <Function test_showhelo[smtp.gmail.com]>
        <Function test_showhelo[mail.python.org]>

{pytest-8.4.0 → pytest-8.4.2}/doc/en/how-to/parametrize.rst

@@ -240,6 +240,13 @@ command line option and the parametrization of our test function:
         if "stringinput" in metafunc.fixturenames:
             metafunc.parametrize("stringinput", metafunc.config.getoption("stringinput"))
 
+.. note::
+
+    The :hook:`pytest_generate_tests` hook can also be implemented directly in a test
+    module or inside a test class; unlike other hooks, pytest will discover it there
+    as well. Other hooks must live in a :ref:`conftest.py <localplugin>` or a plugin.
+    See :ref:`writinghooks`.
+
 If we now pass two stringinput values, our test will run twice:
 
 .. code-block:: pytest

{pytest-8.4.0 → pytest-8.4.2}/doc/en/how-to/plugins.rst

@@ -154,7 +154,10 @@ manually specify each plugin with ``-p`` or :envvar:`PYTEST_PLUGINS`, you can us
 .. code-block:: ini
 
     [pytest]
-    addopts = --disable-plugin-autoload -p NAME,NAME2
+    addopts =
+            --disable-plugin-autoload
+            -p NAME
+            -p NAME2
 
 .. versionadded:: 8.4
 

{pytest-8.4.0 → pytest-8.4.2}/doc/en/how-to/writing_hook_functions.rst

@@ -235,6 +235,12 @@ Example:
         """
         print(config.hook)
 
+.. note::
+
+    Unlike other hooks, the :hook:`pytest_generate_tests` hook is also discovered when
+    defined inside a test module or test class. Other hooks must live in
+    :ref:`conftest.py plugins <localplugin>` or external plugins.
+    See :ref:`parametrize-basics` and the :ref:`hook-reference`.
 
 .. _`addoptionhooks`:
 

{pytest-8.4.0 → pytest-8.4.2}/doc/en/index.rst

@@ -2,7 +2,7 @@
 
 .. sidebar:: **Next Open Trainings and Events**
 
-    - `pytest - simple, rapid and fun testing with Python <https://ep2025.europython.eu/session/pytest-simple-rapid-and-fun-testing-with-python/>`_, at `EuroPython 2025 <https://ep2025.europython.eu/>`_, **July 14th** (3h), Prague, Czech Republic
+    - `Testen mit pytest <https://www.letsboot.ch/kurs/pytest>`_ (German), via `Letsboot <https://www.letsboot.ch/>`_ (3 day in-depth training), **October 29th -- 31st**, Zurich (CH)
     - `Professional Testing with Python <https://python-academy.com/courses/python_course_testing.html>`_, via `Python Academy <https://www.python-academy.com/>`_ (3 day in-depth training), **March 3th -- 5th 2026**, Leipzig (DE) / Remote
 
     Also see :doc:`previous talks and blogposts <talks>`

{pytest-8.4.0 → pytest-8.4.2}/doc/en/reference/reference.rst

@@ -1274,6 +1274,9 @@ Custom warnings generated in some situations such as improper usage or deprecate
 .. autoclass:: pytest.PytestExperimentalApiWarning
    :show-inheritance:
 
+.. autoclass:: pytest.PytestReturnNotNoneWarning
+  :show-inheritance:
+
 .. autoclass:: pytest.PytestRemovedIn9Warning
   :show-inheritance:
 

{pytest-8.4.0 → pytest-8.4.2}/pyproject.toml

@@ -426,6 +426,9 @@ markers = [
     "slow",
     # experimental mark for all tests using pexpect
     "uses_pexpect",
+    # Disables the `remove_ci_env_var` autouse fixture on a given test that
+    # actually inspects whether the CI environment variable is set.
+    "keep_ci_var",
 ]
 
 [tool.towncrier]

{pytest-8.4.0 → pytest-8.4.2}/scripts/prepare-release-pr.py

@@ -135,6 +135,7 @@ def prepare_release_pr(base_branch: str, is_major: bool, prerelease: str) -> Non
             f"--head={release_branch}",
             f"--title=Release {version}",
             f"--body={body}",
+            "--draft",
         ],
         check=True,
     )

{pytest-8.4.0 → pytest-8.4.2}/src/_pytest/_version.py

@@ -1,7 +1,14 @@
 # file generated by setuptools-scm
 # don't change, don't track in version control
 
-__all__ = ["__version__", "__version_tuple__", "version", "version_tuple"]
+__all__ = [
+    "__version__",
+    "__version_tuple__",
+    "version",
+    "version_tuple",
+    "__commit_id__",
+    "commit_id",
+]
 
 TYPE_CHECKING = False
 if TYPE_CHECKING:
@@ -9,13 +16,19 @@ if TYPE_CHECKING:
     from typing import Union
 
     VERSION_TUPLE = Tuple[Union[int, str], ...]
+    COMMIT_ID = Union[str, None]
 else:
     VERSION_TUPLE = object
+    COMMIT_ID = object
 
 version: str
 __version__: str
 __version_tuple__: VERSION_TUPLE
 version_tuple: VERSION_TUPLE
+commit_id: COMMIT_ID
+__commit_id__: COMMIT_ID
 
-__version__ = version = '8.4.0'
-__version_tuple__ = version_tuple = (8, 4, 0)
+__version__ = version = '8.4.2'
+__version_tuple__ = version_tuple = (8, 4, 2)
+
+__commit_id__ = commit_id = None

{pytest-8.4.0 → pytest-8.4.2}/src/_pytest/capture.py

@@ -1043,7 +1043,7 @@ def capteesys(request: SubRequest) -> Generator[CaptureFixture[str]]:
 
     .. code-block:: python
 
-        def test_output(capsys):
+        def test_output(capteesys):
             print("hello")
             captured = capteesys.readouterr()
             assert captured.out == "hello\n"

{pytest-8.4.0 → pytest-8.4.2}/src/_pytest/compat.py

@@ -8,7 +8,7 @@ import enum
 import functools
 import inspect
 from inspect import Parameter
-from inspect import signature
+from inspect import Signature
 import os
 from pathlib import Path
 import sys
@@ -19,6 +19,10 @@ from typing import NoReturn
 import py
 
 
+if sys.version_info >= (3, 14):
+    from annotationlib import Format
+
+
 #: constant to prepare valuing pylib path replacements/lazy proxies later on
 #  intended for removal in pytest 8.0 or 9.0
 
@@ -60,6 +64,13 @@ def is_async_function(func: object) -> bool:
     return iscoroutinefunction(func) or inspect.isasyncgenfunction(func)
 
 
+def signature(obj: Callable[..., Any]) -> Signature:
+    """Return signature without evaluating annotations."""
+    if sys.version_info >= (3, 14):
+        return inspect.signature(obj, annotation_format=Format.STRING)
+    return inspect.signature(obj)
+
+
 def getlocation(function, curdir: str | os.PathLike[str] | None = None) -> str:
     function = get_real_func(function)
     fn = Path(inspect.getfile(function))
@@ -300,3 +311,23 @@ def get_user_id() -> int | None:
 # This also work for Enums (if you use `is` to compare) and Literals.
 def assert_never(value: NoReturn) -> NoReturn:
     assert False, f"Unhandled value: {value} ({type(value).__name__})"
+
+
+class CallableBool:
+    """
+    A bool-like object that can also be called, returning its true/false value.
+
+    Used for backwards compatibility in cases where something was supposed to be a method
+    but was implemented as a simple attribute by mistake (see `TerminalReporter.isatty`).
+
+    Do not use in new code.
+    """
+
+    def __init__(self, value: bool) -> None:
+        self._value = value
+
+    def __bool__(self) -> bool:
+        return self._value
+
+    def __call__(self) -> bool:
+        return self._value

{pytest-8.4.0 → pytest-8.4.2}/src/_pytest/config/argparsing.py

@@ -174,7 +174,9 @@ class Parser:
         self,
         name: str,
         help: str,
-        type: Literal["string", "paths", "pathlist", "args", "linelist", "bool"]
+        type: Literal[
+            "string", "paths", "pathlist", "args", "linelist", "bool", "int", "float"
+        ]
         | None = None,
         default: Any = NOT_SET,
     ) -> None: