@@ -163,9 +163,9 @@ Quick Reference
163163
164164 .. [#cols ] Columns:
165165
166- **"O" **: set on :c:type : `PyBaseObject_Type `
166+ **"O" **: set on :c:data : `PyBaseObject_Type `
167167
168- **"T" **: set on :c:type : `PyType_Type `
168+ **"T" **: set on :c:data : `PyType_Type `
169169
170170 **"D" **: default (if slot is set to ``NULL ``)
171171
@@ -569,8 +569,8 @@ PyTypeObject Slots
569569
570570Each slot has a section describing inheritance. If :c:func: `PyType_Ready `
571571may set a value when the field is set to ``NULL `` then there will also be
572- a "Default" section. (Note that many fields set on :c:type : `PyBaseObject_Type `
573- and :c:type : `PyType_Type ` effectively act as defaults.)
572+ a "Default" section. (Note that many fields set on :c:data : `PyBaseObject_Type `
573+ and :c:data : `PyType_Type ` effectively act as defaults.)
574574
575575.. c :member :: const char * PyTypeObject.tp_name
576576
@@ -964,7 +964,7 @@ and :c:type:`PyType_Type` effectively act as defaults.)
964964
965965 **Default: **
966966
967- :c:type : `PyBaseObject_Type ` uses :c:func: `PyObject_GenericGetAttr `.
967+ :c:data : `PyBaseObject_Type ` uses :c:func: `PyObject_GenericGetAttr `.
968968
969969
970970.. c :member :: setattrofunc PyTypeObject.tp_setattro
@@ -990,7 +990,7 @@ and :c:type:`PyType_Type` effectively act as defaults.)
990990
991991 **Default: **
992992
993- :c:type : `PyBaseObject_Type ` uses :c:func: `PyObject_GenericSetAttr `.
993+ :c:data : `PyBaseObject_Type ` uses :c:func: `PyObject_GenericSetAttr `.
994994
995995
996996.. c :member :: PyBufferProcs* PyTypeObject.tp_as_buffer
@@ -1031,7 +1031,7 @@ and :c:type:`PyType_Type` effectively act as defaults.)
10311031
10321032 **Default: **
10331033
1034- :c:type : `PyBaseObject_Type ` uses
1034+ :c:data : `PyBaseObject_Type ` uses
10351035 ``Py_TPFLAGS_DEFAULT | Py_TPFLAGS_BASETYPE ``.
10361036
10371037 **Bit Masks: **
@@ -1556,7 +1556,7 @@ and :c:type:`PyType_Type` effectively act as defaults.)
15561556
15571557 **Default: **
15581558
1559- :c:type : `PyBaseObject_Type ` provides a :attr: `tp_richcompare `
1559+ :c:data : `PyBaseObject_Type ` provides a :attr: `tp_richcompare `
15601560 implementation, which may be inherited. However, if only
15611561 :attr: `tp_hash ` is defined, not even the inherited function is used
15621562 and instances of the type will not be able to participate in any
@@ -1878,7 +1878,7 @@ and :c:type:`PyType_Type` effectively act as defaults.)
18781878 :c:func: `PyType_GenericAlloc `, to force a standard heap
18791879 allocation strategy.
18801880
1881- For static subtypes, :c:type : `PyBaseObject_Type ` uses
1881+ For static subtypes, :c:data : `PyBaseObject_Type ` uses
18821882 :c:func: `PyType_GenericAlloc `. That is the recommended value
18831883 for all statically defined types.
18841884
@@ -1941,7 +1941,7 @@ and :c:type:`PyType_Type` effectively act as defaults.)
19411941 match :c:func: `PyType_GenericAlloc ` and the value of the
19421942 :c:macro: `Py_TPFLAGS_HAVE_GC ` flag bit.
19431943
1944- For static subtypes, :c:type : `PyBaseObject_Type ` uses PyObject_Del.
1944+ For static subtypes, :c:data : `PyBaseObject_Type ` uses :c:func: ` PyObject_Del ` .
19451945
19461946
19471947.. c :member :: inquiry PyTypeObject.tp_is_gc
0 commit comments