@@ -529,19 +529,19 @@ The following functions and structs are used to create
529529
530530      The following “offset” fields cannot be set using :c:type: `PyType_Slot `: 
531531
532-           * :c:member: `~PyTypeObject.tp_weaklistoffset ` 
533-             (use :c:macro: `Py_TPFLAGS_MANAGED_WEAKREF ` instead if possible) 
534-           * :c:member:`~PyTypeObject.tp_dictoffset` 
535-             (use :c:macro: `Py_TPFLAGS_MANAGED_DICT ` instead if possible) 
536-           * :c:member:`~PyTypeObject.tp_vectorcall_offset` 
537-             (use ``"__vectorcalloffset__" `` in 
538-             :ref: `PyMemberDef  <pymemberdef-offsets >`) 
539- 
540-           If it is not possible to switch to a ``MANAGED`` flag (for example, 
541-           for vectorcall or to support Python older than 3.12), specify the 
542-           offset in :c:member:`Py_tp_members <PyTypeObject.tp_members>`. 
543-           See :ref:`PyMemberDef documentation <pymemberdef-offsets>` 
544-           for details. 
532+       * :c:member: `~PyTypeObject.tp_weaklistoffset ` 
533+         (use :c:macro: `Py_TPFLAGS_MANAGED_WEAKREF ` instead if possible) 
534+       * :c:member:`~PyTypeObject.tp_dictoffset` 
535+         (use :c:macro: `Py_TPFLAGS_MANAGED_DICT ` instead if possible) 
536+       * :c:member:`~PyTypeObject.tp_vectorcall_offset` 
537+         (use ``"__vectorcalloffset__" `` in 
538+         :ref: `PyMemberDef  <pymemberdef-offsets >`) 
539+ 
540+       If it is not possible to switch to a ``MANAGED`` flag (for example, 
541+       for vectorcall or to support Python older than 3.12), specify the 
542+       offset in :c:member:`Py_tp_members <PyTypeObject.tp_members>`. 
543+       See :ref:`PyMemberDef documentation <pymemberdef-offsets>` 
544+       for details. 
545545
546546      The following internal fields cannot be set at all when creating a heap 
547547      type: 
@@ -557,20 +557,18 @@ The following functions and structs are used to create
557557      To avoid issues, use the *bases* argument of 
558558      :c:func:`PyType_FromSpecWithBases` instead. 
559559
560-      .. versionchanged:: 3.9 
561- 
562-         Slots in :c:type:`PyBufferProcs` may be set in the unlimited API. 
560+       .. versionchanged:: 3.9 
561+          Slots in :c:type:`PyBufferProcs` may be set in the unlimited API. 
563562
564-      .. versionchanged:: 3.11 
565-         :c:member:`~PyBufferProcs.bf_getbuffer` and 
566-         :c:member:`~PyBufferProcs.bf_releasebuffer` are now available 
567-         under the :ref:`limited API <limited-c-api>`. 
563+        .. versionchanged:: 3.11 
564+           :c:member:`~PyBufferProcs.bf_getbuffer` and 
565+           :c:member:`~PyBufferProcs.bf_releasebuffer` are now available 
566+           under the :ref:`limited API <limited-c-api>`. 
568567
569-      .. versionchanged:: 3.14 
570- 
571-         The field :c:member:`~PyTypeObject.tp_vectorcall` can now set 
572-         using ``Py_tp_vectorcall``.  See the field's documentation 
573-         for details. 
568+       .. versionchanged:: 3.14 
569+          The field :c:member:`~PyTypeObject.tp_vectorcall` can now set 
570+          using ``Py_tp_vectorcall``.  See the field's documentation 
571+          for details. 
574572
575573   .. c:member:: void *pfunc 
576574
0 commit comments