[3.13] gh-132221: Fix __match_args__ generation docs in dataclasses.rst (GH-132222) (#132226)

gh-132221: Fix `__match_args__` generation docs in `dataclasses.rst` (GH-132222)
(cherry picked from commit 8b62374b34)

Co-authored-by: sobolevn <mail@sobolevn.me>
This commit is contained in:
Miss Islington (bot) 2025-04-07 16:52:55 +02:00 committed by GitHub
parent 3b60cd8ec9
commit bd2f518555
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -164,7 +164,7 @@ Module contents
- *match_args*: If true (the default is ``True``), the
:attr:`~object.__match_args__` tuple will be created from the list of
parameters to the generated :meth:`~object.__init__` method (even if
non keyword-only parameters to the generated :meth:`~object.__init__` method (even if
:meth:`!__init__` is not generated, see above). If false, or if
:attr:`!__match_args__` is already defined in the class, then
:attr:`!__match_args__` will not be generated.
@ -175,11 +175,12 @@ Module contents
fields will be marked as keyword-only. If a field is marked as
keyword-only, then the only effect is that the :meth:`~object.__init__`
parameter generated from a keyword-only field must be specified
with a keyword when :meth:`!__init__` is called. There is no
effect on any other aspect of dataclasses. See the
:term:`parameter` glossary entry for details. Also see the
with a keyword when :meth:`!__init__` is called. See the :term:`parameter`
glossary entry for details. Also see the
:const:`KW_ONLY` section.
Keyword-only fields are not included in :attr:`!__match_args__`.
.. versionadded:: 3.10
- *slots*: If true (the default is ``False``), :attr:`~object.__slots__` attribute
@ -306,6 +307,8 @@ Module contents
This is used when the generated :meth:`~object.__init__` method's
parameters are computed.
Keyword-only fields are also not included in :attr:`!__match_args__`.
.. versionadded:: 3.10
If the default value of a field is specified by a call to