From 0256c38c54730e9bcf3e61031423855655dd8736 Mon Sep 17 00:00:00 2001 From: Eric Traut Date: Wed, 10 Apr 2024 17:57:41 -0700 Subject: [PATCH] =?UTF-8?q?Fixed=20some=20formatting=20issues=20in=20the?= =?UTF-8?q?=20new=20"constructor"=20chapter=20that=20ca=E2=80=A6=20(#1708)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixed some formatting issues in the new "constructor" chapter that caused problems in the table of contents. --- docs/spec/constructors.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/spec/constructors.rst b/docs/spec/constructors.rst index e08996788..00b7ccf34 100644 --- a/docs/spec/constructors.rst +++ b/docs/spec/constructors.rst @@ -18,7 +18,7 @@ Type checkers should mirror this runtime behavior when analyzing a constructor call. Metaclass ``__call__`` Method -============================= +----------------------------- When evaluating a constructor call, a type checker should first check if the class has a custom metaclass (a subclass of ``type``) that defines a ``__call__`` @@ -52,7 +52,7 @@ the ``cls`` parameter. ``__new__`` Method -================== +------------------ After the metaclass ``__call__`` method has been evaluated, a type checker should evaluate the ``__new__`` method of the class (if applicable) using @@ -173,7 +173,7 @@ errors that arise during binding. ``__init__`` Method -=================== +------------------- After evaluating the ``__new__`` method, a type checker should evaluate the ``__init__`` method (if applicable) using the supplied arguments. If the class @@ -274,7 +274,7 @@ within a type annotation for the ``self`` parameter in an ``__init__`` method. Classes Without ``__new__`` and ``__init__`` Methods -==================================================== +---------------------------------------------------- If a class does not define a ``__new__`` method or ``__init__`` method and does not inherit either of these methods from a base class other than