From b6cb36574d0bdf9c4aa2250640d2a2f284ba7bb9 Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Sun, 14 Apr 2024 10:10:07 +0200 Subject: [PATCH] [3.12] dataclasses docs: add some link anchors (GH-117601) (#117863) dataclasses docs: add some link anchors (GH-117601) (cherry picked from commit c99d374fc7327ebd47e22c3b1906bc865aad80a1) Co-authored-by: Jelle Zijlstra --- Doc/library/dataclasses.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/Doc/library/dataclasses.rst b/Doc/library/dataclasses.rst index ae90d85e8d3..95b746d81df 100644 --- a/Doc/library/dataclasses.rst +++ b/Doc/library/dataclasses.rst @@ -554,6 +554,8 @@ See the section below on init-only variables for ways to pass parameters to :meth:`!__post_init__`. Also see the warning about how :func:`replace` handles ``init=False`` fields. +.. _dataclasses-class-variables: + Class variables --------------- @@ -565,6 +567,8 @@ from consideration as a field and is ignored by the dataclass mechanisms. Such ``ClassVar`` pseudo-fields are not returned by the module-level :func:`fields` function. +.. _dataclasses-init-only-variables: + Init-only variables ------------------- @@ -596,6 +600,8 @@ value is not provided when creating the class:: In this case, :func:`fields` will return :class:`Field` objects for ``i`` and ``j``, but not for ``database``. +.. _dataclasses-frozen: + Frozen instances ---------------- @@ -609,6 +615,8 @@ There is a tiny performance penalty when using ``frozen=True``: :meth:`~object.__init__` cannot use simple assignment to initialize fields, and must use :meth:`!__setattr__`. +.. _dataclasses-inheritance: + Inheritance -----------