# Copyright (C) 2001-2018, Python Software Foundation # For licence information, see README file. # msgid "" msgstr "" "Project-Id-Version: Python 3.6\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-11-15 18:54+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: FRENCH \n" "Language: fr\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../Doc/c-api/typeobj.rst:6 msgid "Type Objects" msgstr "Objets type" #: ../Doc/c-api/typeobj.rst:8 msgid "" "Perhaps one of the most important structures of the Python object system is " "the structure that defines a new type: the :c:type:`PyTypeObject` " "structure. Type objects can be handled using any of the :c:func:`PyObject_" "\\*` or :c:func:`PyType_\\*` functions, but do not offer much that's " "interesting to most Python applications. These objects are fundamental to " "how objects behave, so they are very important to the interpreter itself and " "to any extension module that implements new types." msgstr "" #: ../Doc/c-api/typeobj.rst:16 msgid "" "Type objects are fairly large compared to most of the standard types. The " "reason for the size is that each type object stores a large number of " "values, mostly C function pointers, each of which implements a small part of " "the type's functionality. The fields of the type object are examined in " "detail in this section. The fields will be described in the order in which " "they occur in the structure." msgstr "" #: ../Doc/c-api/typeobj.rst:23 msgid "" "In addition to the following quick reference, the :ref:`typedef-examples` " "section provides at-a-glance insight into the meaning and use of :c:type:" "`PyTypeObject`." msgstr "" #: ../Doc/c-api/typeobj.rst:29 msgid "Quick Reference" msgstr "" #: ../Doc/c-api/typeobj.rst:34 msgid "\"tp slots\"" msgstr "" #: ../Doc/c-api/typeobj.rst:40 msgid "PyTypeObject Slot [#slots]_" msgstr "" #: ../Doc/c-api/typeobj.rst:40 ../Doc/c-api/typeobj.rst:200 msgid ":ref:`Type `" msgstr "" #: ../Doc/c-api/typeobj.rst:40 msgid "special methods/attrs" msgstr "" #: ../Doc/c-api/typeobj.rst:40 msgid "Info [#cols]_" msgstr "" #: ../Doc/c-api/typeobj.rst:42 msgid "O" msgstr "O" #: ../Doc/c-api/typeobj.rst:42 msgid "T" msgstr "T" #: ../Doc/c-api/typeobj.rst:42 msgid "D" msgstr "D" #: ../Doc/c-api/typeobj.rst:42 msgid "I" msgstr "" #: ../Doc/c-api/typeobj.rst:44 msgid " :c:member:`~PyTypeObject.tp_name`" msgstr "" #: ../Doc/c-api/typeobj.rst:44 ../Doc/c-api/typeobj.rst:86 #: ../Doc/c-api/typeobj.rst:0 msgid "const char *" msgstr "" #: ../Doc/c-api/typeobj.rst:44 msgid "__name__" msgstr "__name__" #: ../Doc/c-api/typeobj.rst:44 ../Doc/c-api/typeobj.rst:46 #: ../Doc/c-api/typeobj.rst:48 ../Doc/c-api/typeobj.rst:50 #: ../Doc/c-api/typeobj.rst:62 ../Doc/c-api/typeobj.rst:70 #: ../Doc/c-api/typeobj.rst:72 ../Doc/c-api/typeobj.rst:74 #: ../Doc/c-api/typeobj.rst:76 ../Doc/c-api/typeobj.rst:79 #: ../Doc/c-api/typeobj.rst:84 ../Doc/c-api/typeobj.rst:86 #: ../Doc/c-api/typeobj.rst:88 ../Doc/c-api/typeobj.rst:90 #: ../Doc/c-api/typeobj.rst:92 ../Doc/c-api/typeobj.rst:99 #: ../Doc/c-api/typeobj.rst:101 ../Doc/c-api/typeobj.rst:103 #: ../Doc/c-api/typeobj.rst:105 ../Doc/c-api/typeobj.rst:107 #: ../Doc/c-api/typeobj.rst:109 ../Doc/c-api/typeobj.rst:111 #: ../Doc/c-api/typeobj.rst:115 ../Doc/c-api/typeobj.rst:117 #: ../Doc/c-api/typeobj.rst:120 ../Doc/c-api/typeobj.rst:122 #: ../Doc/c-api/typeobj.rst:124 ../Doc/c-api/typeobj.rst:126 #: ../Doc/c-api/typeobj.rst:128 ../Doc/c-api/typeobj.rst:130 #: ../Doc/c-api/typeobj.rst:146 msgid "X" msgstr "" #: ../Doc/c-api/typeobj.rst:46 msgid ":c:member:`~PyTypeObject.tp_basicsize`" msgstr "" #: ../Doc/c-api/typeobj.rst:46 ../Doc/c-api/typeobj.rst:48 #: ../Doc/c-api/typeobj.rst:52 ../Doc/c-api/typeobj.rst:99 #: ../Doc/c-api/typeobj.rst:120 ../Doc/c-api/typeobj.rst:0 #: ../Doc/c-api/typeobj.rst:413 msgid "Py_ssize_t" msgstr "" #: ../Doc/c-api/typeobj.rst:48 msgid ":c:member:`~PyTypeObject.tp_itemsize`" msgstr "" #: ../Doc/c-api/typeobj.rst:50 msgid ":c:member:`~PyTypeObject.tp_dealloc`" msgstr "" #: ../Doc/c-api/typeobj.rst:50 ../Doc/c-api/typeobj.rst:142 #: ../Doc/c-api/typeobj.rst:146 ../Doc/c-api/typeobj.rst:343 msgid ":c:type:`destructor`" msgstr "" #: ../Doc/c-api/typeobj.rst:52 msgid ":c:member:`~PyTypeObject.tp_vectorcall_offset`" msgstr "" #: ../Doc/c-api/typeobj.rst:52 ../Doc/c-api/typeobj.rst:84 #: ../Doc/c-api/typeobj.rst:99 ../Doc/c-api/typeobj.rst:113 #: ../Doc/c-api/typeobj.rst:120 ../Doc/c-api/typeobj.rst:124 #: ../Doc/c-api/typeobj.rst:126 ../Doc/c-api/typeobj.rst:128 msgid "?" msgstr "" #: ../Doc/c-api/typeobj.rst:54 msgid "(:c:member:`~PyTypeObject.tp_getattr`)" msgstr "" #: ../Doc/c-api/typeobj.rst:54 ../Doc/c-api/typeobj.rst:367 msgid ":c:type:`getattrfunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:54 ../Doc/c-api/typeobj.rst:76 msgid "__getattribute__, __getattr__" msgstr "" #: ../Doc/c-api/typeobj.rst:54 ../Doc/c-api/typeobj.rst:57 #: ../Doc/c-api/typeobj.rst:70 ../Doc/c-api/typeobj.rst:76 #: ../Doc/c-api/typeobj.rst:79 ../Doc/c-api/typeobj.rst:88 #: ../Doc/c-api/typeobj.rst:90 ../Doc/c-api/typeobj.rst:92 msgid "G" msgstr "" #: ../Doc/c-api/typeobj.rst:57 msgid "(:c:member:`~PyTypeObject.tp_setattr`)" msgstr "" #: ../Doc/c-api/typeobj.rst:57 ../Doc/c-api/typeobj.rst:372 msgid ":c:type:`setattrfunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:57 ../Doc/c-api/typeobj.rst:79 msgid "__setattr__, __delattr__" msgstr "" #: ../Doc/c-api/typeobj.rst:60 msgid ":c:member:`~PyTypeObject.tp_as_async`" msgstr "" #: ../Doc/c-api/typeobj.rst:60 msgid ":c:type:`PyAsyncMethods` *" msgstr "" #: ../Doc/c-api/typeobj.rst:60 ../Doc/c-api/typeobj.rst:64 #: ../Doc/c-api/typeobj.rst:66 ../Doc/c-api/typeobj.rst:68 msgid ":ref:`sub-slots`" msgstr "" #: ../Doc/c-api/typeobj.rst:60 ../Doc/c-api/typeobj.rst:64 #: ../Doc/c-api/typeobj.rst:66 ../Doc/c-api/typeobj.rst:68 #: ../Doc/c-api/typeobj.rst:82 msgid "%" msgstr "%" #: ../Doc/c-api/typeobj.rst:62 msgid ":c:member:`~PyTypeObject.tp_repr`" msgstr "" #: ../Doc/c-api/typeobj.rst:62 ../Doc/c-api/typeobj.rst:74 #: ../Doc/c-api/typeobj.rst:365 msgid ":c:type:`reprfunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:62 msgid "__repr__" msgstr "" #: ../Doc/c-api/typeobj.rst:64 msgid ":c:member:`~PyTypeObject.tp_as_number`" msgstr "" #: ../Doc/c-api/typeobj.rst:64 msgid ":c:type:`PyNumberMethods` *" msgstr "" #: ../Doc/c-api/typeobj.rst:66 msgid ":c:member:`~PyTypeObject.tp_as_sequence`" msgstr "" #: ../Doc/c-api/typeobj.rst:66 msgid ":c:type:`PySequenceMethods` *" msgstr "" #: ../Doc/c-api/typeobj.rst:68 msgid ":c:member:`~PyTypeObject.tp_as_mapping`" msgstr "" #: ../Doc/c-api/typeobj.rst:68 msgid ":c:type:`PyMappingMethods` *" msgstr "" #: ../Doc/c-api/typeobj.rst:70 msgid ":c:member:`~PyTypeObject.tp_hash`" msgstr "" #: ../Doc/c-api/typeobj.rst:70 ../Doc/c-api/typeobj.rst:401 msgid ":c:type:`hashfunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:70 msgid "__hash__" msgstr "" #: ../Doc/c-api/typeobj.rst:72 msgid ":c:member:`~PyTypeObject.tp_call`" msgstr "" #: ../Doc/c-api/typeobj.rst:72 ../Doc/c-api/typeobj.rst:234 #: ../Doc/c-api/typeobj.rst:237 ../Doc/c-api/typeobj.rst:437 msgid ":c:type:`ternaryfunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:72 msgid "__call__" msgstr "" #: ../Doc/c-api/typeobj.rst:74 msgid ":c:member:`~PyTypeObject.tp_str`" msgstr "" #: ../Doc/c-api/typeobj.rst:74 msgid "__str__" msgstr "" #: ../Doc/c-api/typeobj.rst:76 msgid ":c:member:`~PyTypeObject.tp_getattro`" msgstr "" #: ../Doc/c-api/typeobj.rst:76 ../Doc/c-api/typeobj.rst:378 msgid ":c:type:`getattrofunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:79 msgid ":c:member:`~PyTypeObject.tp_setattro`" msgstr "" #: ../Doc/c-api/typeobj.rst:79 ../Doc/c-api/typeobj.rst:383 msgid ":c:type:`setattrofunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:82 msgid ":c:member:`~PyTypeObject.tp_as_buffer`" msgstr "" #: ../Doc/c-api/typeobj.rst:82 msgid ":c:type:`PyBufferProcs` *" msgstr "" #: ../Doc/c-api/typeobj.rst:84 msgid ":c:member:`~PyTypeObject.tp_flags`" msgstr "" #: ../Doc/c-api/typeobj.rst:84 msgid "unsigned long" msgstr "``unsigned long``" #: ../Doc/c-api/typeobj.rst:86 msgid ":c:member:`~PyTypeObject.tp_doc`" msgstr "" #: ../Doc/c-api/typeobj.rst:86 msgid "__doc__" msgstr "__doc__" #: ../Doc/c-api/typeobj.rst:88 msgid ":c:member:`~PyTypeObject.tp_traverse`" msgstr "" #: ../Doc/c-api/typeobj.rst:88 ../Doc/c-api/typeobj.rst:347 msgid ":c:type:`traverseproc`" msgstr "" #: ../Doc/c-api/typeobj.rst:90 msgid ":c:member:`~PyTypeObject.tp_clear`" msgstr "" #: ../Doc/c-api/typeobj.rst:90 ../Doc/c-api/typeobj.rst:130 #: ../Doc/c-api/typeobj.rst:245 ../Doc/c-api/typeobj.rst:426 msgid ":c:type:`inquiry`" msgstr "" #: ../Doc/c-api/typeobj.rst:92 msgid ":c:member:`~PyTypeObject.tp_richcompare`" msgstr "" #: ../Doc/c-api/typeobj.rst:92 ../Doc/c-api/typeobj.rst:403 msgid ":c:type:`richcmpfunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:92 msgid "__lt__, __le__, __eq__, __ne__, __gt__, __ge__" msgstr "" #: ../Doc/c-api/typeobj.rst:99 msgid ":c:member:`~PyTypeObject.tp_weaklistoffset`" msgstr "" #: ../Doc/c-api/typeobj.rst:101 msgid ":c:member:`~PyTypeObject.tp_iter`" msgstr "" #: ../Doc/c-api/typeobj.rst:101 ../Doc/c-api/typeobj.rst:409 msgid ":c:type:`getiterfunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:101 msgid "__iter__" msgstr "" #: ../Doc/c-api/typeobj.rst:103 msgid ":c:member:`~PyTypeObject.tp_iternext`" msgstr "" #: ../Doc/c-api/typeobj.rst:103 ../Doc/c-api/typeobj.rst:411 msgid ":c:type:`iternextfunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:103 msgid "__next__" msgstr "" #: ../Doc/c-api/typeobj.rst:105 msgid ":c:member:`~PyTypeObject.tp_methods`" msgstr "" #: ../Doc/c-api/typeobj.rst:105 msgid ":c:type:`PyMethodDef` []" msgstr "" #: ../Doc/c-api/typeobj.rst:107 msgid ":c:member:`~PyTypeObject.tp_members`" msgstr "" #: ../Doc/c-api/typeobj.rst:107 msgid ":c:type:`PyMemberDef` []" msgstr "" #: ../Doc/c-api/typeobj.rst:109 msgid ":c:member:`~PyTypeObject.tp_getset`" msgstr "" #: ../Doc/c-api/typeobj.rst:109 msgid ":c:type:`PyGetSetDef` []" msgstr "" #: ../Doc/c-api/typeobj.rst:111 msgid ":c:member:`~PyTypeObject.tp_base`" msgstr "" #: ../Doc/c-api/typeobj.rst:111 ../Doc/c-api/typeobj.rst:0 msgid ":c:type:`PyTypeObject` *" msgstr "" #: ../Doc/c-api/typeobj.rst:111 msgid "__base__" msgstr "" #: ../Doc/c-api/typeobj.rst:113 msgid ":c:member:`~PyTypeObject.tp_dict`" msgstr "" #: ../Doc/c-api/typeobj.rst:113 ../Doc/c-api/typeobj.rst:132 #: ../Doc/c-api/typeobj.rst:134 ../Doc/c-api/typeobj.rst:136 #: ../Doc/c-api/typeobj.rst:138 ../Doc/c-api/typeobj.rst:140 #: ../Doc/c-api/typeobj.rst:338 ../Doc/c-api/typeobj.rst:0 #: ../Doc/c-api/typeobj.rst:353 ../Doc/c-api/typeobj.rst:365 #: ../Doc/c-api/typeobj.rst:367 ../Doc/c-api/typeobj.rst:378 #: ../Doc/c-api/typeobj.rst:389 ../Doc/c-api/typeobj.rst:401 #: ../Doc/c-api/typeobj.rst:403 ../Doc/c-api/typeobj.rst:409 #: ../Doc/c-api/typeobj.rst:411 ../Doc/c-api/typeobj.rst:413 #: ../Doc/c-api/typeobj.rst:428 ../Doc/c-api/typeobj.rst:432 #: ../Doc/c-api/typeobj.rst:437 ../Doc/c-api/typeobj.rst:443 msgid ":c:type:`PyObject` *" msgstr "" #: ../Doc/c-api/typeobj.rst:113 msgid "__dict__" msgstr "" #: ../Doc/c-api/typeobj.rst:115 msgid ":c:member:`~PyTypeObject.tp_descr_get`" msgstr "" #: ../Doc/c-api/typeobj.rst:115 ../Doc/c-api/typeobj.rst:389 msgid ":c:type:`descrgetfunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:115 msgid "__get__" msgstr "" #: ../Doc/c-api/typeobj.rst:117 msgid ":c:member:`~PyTypeObject.tp_descr_set`" msgstr "" #: ../Doc/c-api/typeobj.rst:117 ../Doc/c-api/typeobj.rst:395 msgid ":c:type:`descrsetfunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:117 msgid "__set__, __delete__" msgstr "" #: ../Doc/c-api/typeobj.rst:120 msgid ":c:member:`~PyTypeObject.tp_dictoffset`" msgstr "" #: ../Doc/c-api/typeobj.rst:122 msgid ":c:member:`~PyTypeObject.tp_init`" msgstr "" #: ../Doc/c-api/typeobj.rst:122 ../Doc/c-api/typeobj.rst:359 msgid ":c:type:`initproc`" msgstr "" #: ../Doc/c-api/typeobj.rst:122 msgid "__init__" msgstr "" #: ../Doc/c-api/typeobj.rst:124 msgid ":c:member:`~PyTypeObject.tp_alloc`" msgstr "" #: ../Doc/c-api/typeobj.rst:124 ../Doc/c-api/typeobj.rst:338 msgid ":c:type:`allocfunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:126 msgid ":c:member:`~PyTypeObject.tp_new`" msgstr "" #: ../Doc/c-api/typeobj.rst:126 ../Doc/c-api/typeobj.rst:353 msgid ":c:type:`newfunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:126 msgid "__new__" msgstr "" #: ../Doc/c-api/typeobj.rst:128 msgid ":c:member:`~PyTypeObject.tp_free`" msgstr "" #: ../Doc/c-api/typeobj.rst:128 ../Doc/c-api/typeobj.rst:345 msgid ":c:type:`freefunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:130 msgid ":c:member:`~PyTypeObject.tp_is_gc`" msgstr "" #: ../Doc/c-api/typeobj.rst:132 msgid "<:c:member:`~PyTypeObject.tp_bases`>" msgstr "" #: ../Doc/c-api/typeobj.rst:132 msgid "__bases__" msgstr "" #: ../Doc/c-api/typeobj.rst:132 ../Doc/c-api/typeobj.rst:134 msgid "~" msgstr "" #: ../Doc/c-api/typeobj.rst:134 msgid "<:c:member:`~PyTypeObject.tp_mro`>" msgstr "" #: ../Doc/c-api/typeobj.rst:134 msgid "__mro__" msgstr "" #: ../Doc/c-api/typeobj.rst:136 msgid "[:c:member:`~PyTypeObject.tp_cache`]" msgstr "" #: ../Doc/c-api/typeobj.rst:138 msgid "[:c:member:`~PyTypeObject.tp_subclasses`]" msgstr "" #: ../Doc/c-api/typeobj.rst:138 msgid "__subclasses__" msgstr "" #: ../Doc/c-api/typeobj.rst:140 msgid "[:c:member:`~PyTypeObject.tp_weaklist`]" msgstr "" #: ../Doc/c-api/typeobj.rst:142 msgid "(:c:member:`~PyTypeObject.tp_del`)" msgstr "" #: ../Doc/c-api/typeobj.rst:144 msgid "[:c:member:`~PyTypeObject.tp_version_tag`]" msgstr "" #: ../Doc/c-api/typeobj.rst:144 msgid "unsigned int" msgstr "``unsigned int``" #: ../Doc/c-api/typeobj.rst:146 msgid ":c:member:`~PyTypeObject.tp_finalize`" msgstr "" #: ../Doc/c-api/typeobj.rst:146 msgid "__del__" msgstr "" #: ../Doc/c-api/typeobj.rst:149 msgid "" "If :const:`COUNT_ALLOCS` is defined then the following (internal-only) " "fields exist as well:" msgstr "" #: ../Doc/c-api/typeobj.rst:152 msgid ":c:member:`~PyTypeObject.tp_allocs`" msgstr "" #: ../Doc/c-api/typeobj.rst:153 msgid ":c:member:`~PyTypeObject.tp_frees`" msgstr "" #: ../Doc/c-api/typeobj.rst:154 msgid ":c:member:`~PyTypeObject.tp_maxalloc`" msgstr "" #: ../Doc/c-api/typeobj.rst:155 msgid ":c:member:`~PyTypeObject.tp_prev`" msgstr "" #: ../Doc/c-api/typeobj.rst:156 msgid ":c:member:`~PyTypeObject.tp_next`" msgstr "" #: ../Doc/c-api/typeobj.rst:159 msgid "" "A slot name in parentheses indicates it is (effectively) deprecated. Names " "in angle brackets should be treated as read-only. Names in square brackets " "are for internal use only. \"\" (as a prefix) means the field is required " "(must be non-``NULL``)." msgstr "" #: ../Doc/c-api/typeobj.rst:163 msgid "Columns:" msgstr "" #: ../Doc/c-api/typeobj.rst:165 msgid "**\"O\"**: set on :c:type:`PyBaseObject_Type`" msgstr "" #: ../Doc/c-api/typeobj.rst:167 msgid "**\"T\"**: set on :c:type:`PyType_Type`" msgstr "" #: ../Doc/c-api/typeobj.rst:169 msgid "**\"D\"**: default (if slot is set to ``NULL``)" msgstr "" #: ../Doc/c-api/typeobj.rst:179 msgid "**\"I\"**: inheritance" msgstr "" #: ../Doc/c-api/typeobj.rst:188 msgid "" "Note that some slots are effectively inherited through the normal attribute " "lookup chain." msgstr "" #: ../Doc/c-api/typeobj.rst:194 msgid "sub-slots" msgstr "" #: ../Doc/c-api/typeobj.rst:200 msgid "Slot" msgstr "" #: ../Doc/c-api/typeobj.rst:200 msgid "special methods" msgstr "" #: ../Doc/c-api/typeobj.rst:203 msgid ":c:member:`~PyAsyncMethods.am_await`" msgstr "" #: ../Doc/c-api/typeobj.rst:203 ../Doc/c-api/typeobj.rst:205 #: ../Doc/c-api/typeobj.rst:207 ../Doc/c-api/typeobj.rst:239 #: ../Doc/c-api/typeobj.rst:241 ../Doc/c-api/typeobj.rst:243 #: ../Doc/c-api/typeobj.rst:247 ../Doc/c-api/typeobj.rst:274 #: ../Doc/c-api/typeobj.rst:278 ../Doc/c-api/typeobj.rst:288 #: ../Doc/c-api/typeobj.rst:428 msgid ":c:type:`unaryfunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:203 msgid "__await__" msgstr "" #: ../Doc/c-api/typeobj.rst:205 msgid ":c:member:`~PyAsyncMethods.am_aiter`" msgstr "" #: ../Doc/c-api/typeobj.rst:205 msgid "__aiter__" msgstr "" #: ../Doc/c-api/typeobj.rst:207 msgid ":c:member:`~PyAsyncMethods.am_anext`" msgstr "" #: ../Doc/c-api/typeobj.rst:207 msgid "__anext__" msgstr "" #: ../Doc/c-api/typeobj.rst:211 msgid ":c:member:`~PyNumberMethods.nb_add`" msgstr "" #: ../Doc/c-api/typeobj.rst:211 ../Doc/c-api/typeobj.rst:214 #: ../Doc/c-api/typeobj.rst:216 ../Doc/c-api/typeobj.rst:219 #: ../Doc/c-api/typeobj.rst:221 ../Doc/c-api/typeobj.rst:224 #: ../Doc/c-api/typeobj.rst:226 ../Doc/c-api/typeobj.rst:229 #: ../Doc/c-api/typeobj.rst:231 ../Doc/c-api/typeobj.rst:249 #: ../Doc/c-api/typeobj.rst:252 ../Doc/c-api/typeobj.rst:254 #: ../Doc/c-api/typeobj.rst:257 ../Doc/c-api/typeobj.rst:259 #: ../Doc/c-api/typeobj.rst:262 ../Doc/c-api/typeobj.rst:264 #: ../Doc/c-api/typeobj.rst:267 ../Doc/c-api/typeobj.rst:269 #: ../Doc/c-api/typeobj.rst:272 ../Doc/c-api/typeobj.rst:280 #: ../Doc/c-api/typeobj.rst:282 ../Doc/c-api/typeobj.rst:284 #: ../Doc/c-api/typeobj.rst:286 ../Doc/c-api/typeobj.rst:290 #: ../Doc/c-api/typeobj.rst:293 ../Doc/c-api/typeobj.rst:299 #: ../Doc/c-api/typeobj.rst:308 ../Doc/c-api/typeobj.rst:319 #: ../Doc/c-api/typeobj.rst:432 msgid ":c:type:`binaryfunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:211 msgid "__add__ __radd__" msgstr "" #: ../Doc/c-api/typeobj.rst:214 msgid ":c:member:`~PyNumberMethods.nb_inplace_add`" msgstr "" #: ../Doc/c-api/typeobj.rst:214 ../Doc/c-api/typeobj.rst:319 msgid "__iadd__" msgstr "" #: ../Doc/c-api/typeobj.rst:216 msgid ":c:member:`~PyNumberMethods.nb_subtract`" msgstr "" #: ../Doc/c-api/typeobj.rst:216 msgid "__sub__ __rsub__" msgstr "" #: ../Doc/c-api/typeobj.rst:219 msgid ":c:member:`~PyNumberMethods.nb_inplace_subtract`" msgstr "" #: ../Doc/c-api/typeobj.rst:219 msgid "__sub__" msgstr "" #: ../Doc/c-api/typeobj.rst:221 msgid ":c:member:`~PyNumberMethods.nb_multiply`" msgstr "" #: ../Doc/c-api/typeobj.rst:221 msgid "__mul__ __rmul__" msgstr "" #: ../Doc/c-api/typeobj.rst:224 msgid ":c:member:`~PyNumberMethods.nb_inplace_multiply`" msgstr "" #: ../Doc/c-api/typeobj.rst:224 ../Doc/c-api/typeobj.rst:310 msgid "__mul__" msgstr "" #: ../Doc/c-api/typeobj.rst:226 msgid ":c:member:`~PyNumberMethods.nb_remainder`" msgstr "" #: ../Doc/c-api/typeobj.rst:226 msgid "__mod__ __rmod__" msgstr "" #: ../Doc/c-api/typeobj.rst:229 msgid ":c:member:`~PyNumberMethods.nb_inplace_remainder`" msgstr "" #: ../Doc/c-api/typeobj.rst:229 msgid "__mod__" msgstr "" #: ../Doc/c-api/typeobj.rst:231 msgid ":c:member:`~PyNumberMethods.nb_divmod`" msgstr "" #: ../Doc/c-api/typeobj.rst:231 msgid "__divmod__ __rdivmod__" msgstr "" #: ../Doc/c-api/typeobj.rst:234 msgid ":c:member:`~PyNumberMethods.nb_power`" msgstr "" #: ../Doc/c-api/typeobj.rst:234 msgid "__pow__ __rpow__" msgstr "" #: ../Doc/c-api/typeobj.rst:237 msgid ":c:member:`~PyNumberMethods.nb_inplace_power`" msgstr "" #: ../Doc/c-api/typeobj.rst:237 msgid "__pow__" msgstr "" #: ../Doc/c-api/typeobj.rst:239 msgid ":c:member:`~PyNumberMethods.nb_negative`" msgstr "" #: ../Doc/c-api/typeobj.rst:239 msgid "__neg__" msgstr "" #: ../Doc/c-api/typeobj.rst:241 msgid ":c:member:`~PyNumberMethods.nb_positive`" msgstr "" #: ../Doc/c-api/typeobj.rst:241 msgid "__pos__" msgstr "" #: ../Doc/c-api/typeobj.rst:243 msgid ":c:member:`~PyNumberMethods.nb_absolute`" msgstr "" #: ../Doc/c-api/typeobj.rst:243 msgid "__abs__" msgstr "" #: ../Doc/c-api/typeobj.rst:245 msgid ":c:member:`~PyNumberMethods.nb_bool`" msgstr "" #: ../Doc/c-api/typeobj.rst:245 msgid "__bool__" msgstr "" #: ../Doc/c-api/typeobj.rst:247 msgid ":c:member:`~PyNumberMethods.nb_invert`" msgstr "" #: ../Doc/c-api/typeobj.rst:247 msgid "__invert__" msgstr "" #: ../Doc/c-api/typeobj.rst:249 msgid ":c:member:`~PyNumberMethods.nb_lshift`" msgstr "" #: ../Doc/c-api/typeobj.rst:249 msgid "__lshift__ __rlshift__" msgstr "" #: ../Doc/c-api/typeobj.rst:252 msgid ":c:member:`~PyNumberMethods.nb_inplace_lshift`" msgstr "" #: ../Doc/c-api/typeobj.rst:252 msgid "__lshift__" msgstr "" #: ../Doc/c-api/typeobj.rst:254 msgid ":c:member:`~PyNumberMethods.nb_rshift`" msgstr "" #: ../Doc/c-api/typeobj.rst:254 msgid "__rshift__ __rrshift__" msgstr "" #: ../Doc/c-api/typeobj.rst:257 msgid ":c:member:`~PyNumberMethods.nb_inplace_rshift`" msgstr "" #: ../Doc/c-api/typeobj.rst:257 msgid "__rshift__" msgstr "" #: ../Doc/c-api/typeobj.rst:259 msgid ":c:member:`~PyNumberMethods.nb_and`" msgstr "" #: ../Doc/c-api/typeobj.rst:259 msgid "__and__ __rand__" msgstr "" #: ../Doc/c-api/typeobj.rst:262 msgid ":c:member:`~PyNumberMethods.nb_inplace_and`" msgstr "" #: ../Doc/c-api/typeobj.rst:262 msgid "__and__" msgstr "" #: ../Doc/c-api/typeobj.rst:264 msgid ":c:member:`~PyNumberMethods.nb_xor`" msgstr "" #: ../Doc/c-api/typeobj.rst:264 msgid "__xor__ __rxor__" msgstr "" #: ../Doc/c-api/typeobj.rst:267 msgid ":c:member:`~PyNumberMethods.nb_inplace_xor`" msgstr "" #: ../Doc/c-api/typeobj.rst:267 msgid "__xor__" msgstr "" #: ../Doc/c-api/typeobj.rst:269 msgid ":c:member:`~PyNumberMethods.nb_or`" msgstr "" #: ../Doc/c-api/typeobj.rst:269 msgid "__or__ __ror__" msgstr "" #: ../Doc/c-api/typeobj.rst:272 msgid ":c:member:`~PyNumberMethods.nb_inplace_or`" msgstr "" #: ../Doc/c-api/typeobj.rst:272 msgid "__or__" msgstr "" #: ../Doc/c-api/typeobj.rst:274 msgid ":c:member:`~PyNumberMethods.nb_int`" msgstr "" #: ../Doc/c-api/typeobj.rst:274 msgid "__int__" msgstr "" #: ../Doc/c-api/typeobj.rst:276 msgid ":c:member:`~PyNumberMethods.nb_reserved`" msgstr "" #: ../Doc/c-api/typeobj.rst:276 ../Doc/c-api/typeobj.rst:343 #: ../Doc/c-api/typeobj.rst:345 ../Doc/c-api/typeobj.rst:0 #: ../Doc/c-api/typeobj.rst:426 msgid "void *" msgstr "" #: ../Doc/c-api/typeobj.rst:278 msgid ":c:member:`~PyNumberMethods.nb_float`" msgstr "" #: ../Doc/c-api/typeobj.rst:278 msgid "__float__" msgstr "" #: ../Doc/c-api/typeobj.rst:280 msgid ":c:member:`~PyNumberMethods.nb_floor_divide`" msgstr "" #: ../Doc/c-api/typeobj.rst:280 ../Doc/c-api/typeobj.rst:282 msgid "__floordiv__" msgstr "" #: ../Doc/c-api/typeobj.rst:282 msgid ":c:member:`~PyNumberMethods.nb_inplace_floor_divide`" msgstr "" #: ../Doc/c-api/typeobj.rst:284 msgid ":c:member:`~PyNumberMethods.nb_true_divide`" msgstr "" #: ../Doc/c-api/typeobj.rst:284 ../Doc/c-api/typeobj.rst:286 msgid "__truediv__" msgstr "" #: ../Doc/c-api/typeobj.rst:286 msgid ":c:member:`~PyNumberMethods.nb_inplace_true_divide`" msgstr "" #: ../Doc/c-api/typeobj.rst:288 msgid ":c:member:`~PyNumberMethods.nb_index`" msgstr "" #: ../Doc/c-api/typeobj.rst:288 msgid "__index__" msgstr "" #: ../Doc/c-api/typeobj.rst:290 msgid ":c:member:`~PyNumberMethods.nb_matrix_multiply`" msgstr "" #: ../Doc/c-api/typeobj.rst:290 msgid "__matmul__ __rmatmul__" msgstr "" #: ../Doc/c-api/typeobj.rst:293 msgid ":c:member:`~PyNumberMethods.nb_inplace_matrix_multiply`" msgstr "" #: ../Doc/c-api/typeobj.rst:293 msgid "__matmul__" msgstr "" #: ../Doc/c-api/typeobj.rst:297 msgid ":c:member:`~PyMappingMethods.mp_length`" msgstr "" #: ../Doc/c-api/typeobj.rst:297 ../Doc/c-api/typeobj.rst:306 #: ../Doc/c-api/typeobj.rst:413 msgid ":c:type:`lenfunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:297 ../Doc/c-api/typeobj.rst:306 msgid "__len__" msgstr "" #: ../Doc/c-api/typeobj.rst:299 msgid ":c:member:`~PyMappingMethods.mp_subscript`" msgstr "" #: ../Doc/c-api/typeobj.rst:299 ../Doc/c-api/typeobj.rst:312 msgid "__getitem__" msgstr "" #: ../Doc/c-api/typeobj.rst:301 msgid ":c:member:`~PyMappingMethods.mp_ass_subscript`" msgstr "" #: ../Doc/c-api/typeobj.rst:301 ../Doc/c-api/typeobj.rst:458 msgid ":c:type:`objobjargproc`" msgstr "" #: ../Doc/c-api/typeobj.rst:301 msgid "__setitem__, __delitem__" msgstr "" #: ../Doc/c-api/typeobj.rst:306 msgid ":c:member:`~PySequenceMethods.sq_length`" msgstr "" #: ../Doc/c-api/typeobj.rst:308 msgid ":c:member:`~PySequenceMethods.sq_concat`" msgstr "" #: ../Doc/c-api/typeobj.rst:308 msgid "__add__" msgstr "" #: ../Doc/c-api/typeobj.rst:310 msgid ":c:member:`~PySequenceMethods.sq_repeat`" msgstr "" #: ../Doc/c-api/typeobj.rst:310 ../Doc/c-api/typeobj.rst:312 #: ../Doc/c-api/typeobj.rst:321 ../Doc/c-api/typeobj.rst:443 msgid ":c:type:`ssizeargfunc`" msgstr "" #: ../Doc/c-api/typeobj.rst:312 msgid ":c:member:`~PySequenceMethods.sq_item`" msgstr "" #: ../Doc/c-api/typeobj.rst:314 msgid ":c:member:`~PySequenceMethods.sq_ass_item`" msgstr "" #: ../Doc/c-api/typeobj.rst:314 ../Doc/c-api/typeobj.rst:448 msgid ":c:type:`ssizeobjargproc`" msgstr "" #: ../Doc/c-api/typeobj.rst:314 msgid "__setitem__ __delitem__" msgstr "" #: ../Doc/c-api/typeobj.rst:317 msgid ":c:member:`~PySequenceMethods.sq_contains`" msgstr "" #: ../Doc/c-api/typeobj.rst:317 ../Doc/c-api/typeobj.rst:453 msgid ":c:type:`objobjproc`" msgstr "" #: ../Doc/c-api/typeobj.rst:317 msgid "__contains__" msgstr "" #: ../Doc/c-api/typeobj.rst:319 msgid ":c:member:`~PySequenceMethods.sq_inplace_concat`" msgstr "" #: ../Doc/c-api/typeobj.rst:321 msgid ":c:member:`~PySequenceMethods.sq_inplace_repeat`" msgstr "" #: ../Doc/c-api/typeobj.rst:321 msgid "__imul__" msgstr "" #: ../Doc/c-api/typeobj.rst:325 msgid ":c:member:`~PyBufferProcs.bf_getbuffer`" msgstr "" #: ../Doc/c-api/typeobj.rst:325 msgid ":c:func:`getbufferproc`" msgstr "" #: ../Doc/c-api/typeobj.rst:327 msgid ":c:member:`~PyBufferProcs.bf_releasebuffer`" msgstr "" #: ../Doc/c-api/typeobj.rst:327 msgid ":c:func:`releasebufferproc`" msgstr "" #: ../Doc/c-api/typeobj.rst:333 msgid "slot typedefs" msgstr "" #: ../Doc/c-api/typeobj.rst:336 msgid "typedef" msgstr "" #: ../Doc/c-api/typeobj.rst:336 msgid "Parameter Types" msgstr "" #: ../Doc/c-api/typeobj.rst:336 msgid "Return Type" msgstr "" #: ../Doc/c-api/typeobj.rst:343 ../Doc/c-api/typeobj.rst:345 #: ../Doc/c-api/typeobj.rst:421 msgid "void" msgstr "" #: ../Doc/c-api/typeobj.rst:0 msgid ":c:type:`visitproc`" msgstr "" #: ../Doc/c-api/typeobj.rst:347 ../Doc/c-api/typeobj.rst:359 #: ../Doc/c-api/typeobj.rst:372 ../Doc/c-api/typeobj.rst:383 #: ../Doc/c-api/typeobj.rst:395 ../Doc/c-api/typeobj.rst:0 #: ../Doc/c-api/typeobj.rst:415 ../Doc/c-api/typeobj.rst:426 #: ../Doc/c-api/typeobj.rst:448 ../Doc/c-api/typeobj.rst:453 #: ../Doc/c-api/typeobj.rst:458 msgid "int" msgstr "*int*" #: ../Doc/c-api/typeobj.rst:401 msgid "Py_hash_t" msgstr "" #: ../Doc/c-api/typeobj.rst:415 msgid ":c:type:`getbufferproc`" msgstr "" #: ../Doc/c-api/typeobj.rst:0 msgid ":c:type:`Py_buffer` *" msgstr "" #: ../Doc/c-api/typeobj.rst:421 msgid ":c:type:`releasebufferproc`" msgstr "" #: ../Doc/c-api/typeobj.rst:465 msgid "See :ref:`slot-typedefs` below for more detail." msgstr "" #: ../Doc/c-api/typeobj.rst:469 msgid "PyTypeObject Definition" msgstr "" #: ../Doc/c-api/typeobj.rst:471 msgid "" "The structure definition for :c:type:`PyTypeObject` can be found in :file:" "`Include/object.h`. For convenience of reference, this repeats the " "definition found there:" msgstr "" #: ../Doc/c-api/typeobj.rst:481 #, fuzzy msgid "PyObject Slots" msgstr "Objets type" #: ../Doc/c-api/typeobj.rst:483 msgid "" "The type object structure extends the :c:type:`PyVarObject` structure. The :" "attr:`ob_size` field is used for dynamic types (created by :func:" "`type_new`, usually called from a class statement). Note that :c:data:" "`PyType_Type` (the metatype) initializes :c:member:`~PyTypeObject." "tp_itemsize`, which means that its instances (i.e. type objects) *must* have " "the :attr:`ob_size` field." msgstr "" #: ../Doc/c-api/typeobj.rst:493 msgid "" "These fields are only present when the macro ``Py_TRACE_REFS`` is defined. " "Their initialization to ``NULL`` is taken care of by the " "``PyObject_HEAD_INIT`` macro. For statically allocated objects, these " "fields always remain ``NULL``. For dynamically allocated objects, these two " "fields are used to link the object into a doubly-linked list of *all* live " "objects on the heap. This could be used for various debugging purposes; " "currently the only use is to print the objects that are still alive at the " "end of a run when the environment variable :envvar:`PYTHONDUMPREFS` is set." msgstr "" #: ../Doc/c-api/typeobj.rst:502 ../Doc/c-api/typeobj.rst:515 #: ../Doc/c-api/typeobj.rst:538 ../Doc/c-api/typeobj.rst:551 #: ../Doc/c-api/typeobj.rst:593 ../Doc/c-api/typeobj.rst:636 #: ../Doc/c-api/typeobj.rst:682 ../Doc/c-api/typeobj.rst:738 #: ../Doc/c-api/typeobj.rst:757 ../Doc/c-api/typeobj.rst:774 #: ../Doc/c-api/typeobj.rst:792 ../Doc/c-api/typeobj.rst:816 #: ../Doc/c-api/typeobj.rst:833 ../Doc/c-api/typeobj.rst:845 #: ../Doc/c-api/typeobj.rst:857 ../Doc/c-api/typeobj.rst:890 #: ../Doc/c-api/typeobj.rst:908 ../Doc/c-api/typeobj.rst:928 #: ../Doc/c-api/typeobj.rst:949 ../Doc/c-api/typeobj.rst:975 #: ../Doc/c-api/typeobj.rst:994 ../Doc/c-api/typeobj.rst:1010 #: ../Doc/c-api/typeobj.rst:1047 ../Doc/c-api/typeobj.rst:1058 #: ../Doc/c-api/typeobj.rst:1068 ../Doc/c-api/typeobj.rst:1078 #: ../Doc/c-api/typeobj.rst:1092 ../Doc/c-api/typeobj.rst:1111 #: ../Doc/c-api/typeobj.rst:1134 ../Doc/c-api/typeobj.rst:1179 #: ../Doc/c-api/typeobj.rst:1203 ../Doc/c-api/typeobj.rst:1245 #: ../Doc/c-api/typeobj.rst:1306 ../Doc/c-api/typeobj.rst:1365 #: ../Doc/c-api/typeobj.rst:1395 ../Doc/c-api/typeobj.rst:1427 #: ../Doc/c-api/typeobj.rst:1450 ../Doc/c-api/typeobj.rst:1463 #: ../Doc/c-api/typeobj.rst:1478 ../Doc/c-api/typeobj.rst:1492 #: ../Doc/c-api/typeobj.rst:1522 ../Doc/c-api/typeobj.rst:1542 #: ../Doc/c-api/typeobj.rst:1568 ../Doc/c-api/typeobj.rst:1586 #: ../Doc/c-api/typeobj.rst:1626 ../Doc/c-api/typeobj.rst:1677 #: ../Doc/c-api/typeobj.rst:1694 ../Doc/c-api/typeobj.rst:1732 #: ../Doc/c-api/typeobj.rst:1753 ../Doc/c-api/typeobj.rst:1785 #: ../Doc/c-api/typeobj.rst:1802 ../Doc/c-api/typeobj.rst:1813 #: ../Doc/c-api/typeobj.rst:1823 ../Doc/c-api/typeobj.rst:1832 #: ../Doc/c-api/typeobj.rst:1842 ../Doc/c-api/typeobj.rst:1856 #: ../Doc/c-api/typeobj.rst:1894 msgid "**Inheritance:**" msgstr "" #: ../Doc/c-api/typeobj.rst:504 msgid "These fields are not inherited by subtypes." msgstr "" #: ../Doc/c-api/typeobj.rst:509 msgid "" "This is the type object's reference count, initialized to ``1`` by the " "``PyObject_HEAD_INIT`` macro. Note that for statically allocated type " "objects, the type's instances (objects whose :attr:`ob_type` points back to " "the type) do *not* count as references. But for dynamically allocated type " "objects, the instances *do* count as references." msgstr "" #: ../Doc/c-api/typeobj.rst:517 ../Doc/c-api/typeobj.rst:553 #: ../Doc/c-api/typeobj.rst:595 msgid "This field is not inherited by subtypes." msgstr "" #: ../Doc/c-api/typeobj.rst:522 msgid "" "This is the type's type, in other words its metatype. It is initialized by " "the argument to the ``PyObject_HEAD_INIT`` macro, and its value should " "normally be ``&PyType_Type``. However, for dynamically loadable extension " "modules that must be usable on Windows (at least), the compiler complains " "that this is not a valid initializer. Therefore, the convention is to pass " "``NULL`` to the ``PyObject_HEAD_INIT`` macro and to initialize this field " "explicitly at the start of the module's initialization function, before " "doing anything else. This is typically done like this::" msgstr "" #: ../Doc/c-api/typeobj.rst:533 msgid "" "This should be done before any instances of the type are created. :c:func:" "`PyType_Ready` checks if :attr:`ob_type` is ``NULL``, and if so, initializes " "it to the :attr:`ob_type` field of the base class. :c:func:`PyType_Ready` " "will not change this field if it is non-zero." msgstr "" #: ../Doc/c-api/typeobj.rst:540 ../Doc/c-api/typeobj.rst:684 #: ../Doc/c-api/typeobj.rst:818 ../Doc/c-api/typeobj.rst:910 #: ../Doc/c-api/typeobj.rst:930 ../Doc/c-api/typeobj.rst:1429 #: ../Doc/c-api/typeobj.rst:1452 ../Doc/c-api/typeobj.rst:1570 #: ../Doc/c-api/typeobj.rst:1588 ../Doc/c-api/typeobj.rst:1679 #: ../Doc/c-api/typeobj.rst:1787 ../Doc/c-api/typeobj.rst:1896 msgid "This field is inherited by subtypes." msgstr "" #: ../Doc/c-api/typeobj.rst:544 msgid "PyVarObject Slots" msgstr "" #: ../Doc/c-api/typeobj.rst:548 msgid "" "For statically allocated type objects, this should be initialized to zero. " "For dynamically allocated type objects, this field has a special internal " "meaning." msgstr "" #: ../Doc/c-api/typeobj.rst:557 #, fuzzy msgid "PyTypeObject Slots" msgstr "Objets type" #: ../Doc/c-api/typeobj.rst:559 msgid "" "Each slot has a section describing inheritance. If :c:func:`PyType_Ready` " "may set a value when the field is set to ``NULL`` then there will also be a " "\"Default\" section. (Note that many fields set on :c:type:" "`PyBaseObject_Type` and :c:type:`PyType_Type` effectively act as defaults.)" msgstr "" #: ../Doc/c-api/typeobj.rst:566 msgid "" "Pointer to a NUL-terminated string containing the name of the type. For " "types that are accessible as module globals, the string should be the full " "module name, followed by a dot, followed by the type name; for built-in " "types, it should be just the type name. If the module is a submodule of a " "package, the full package name is part of the full module name. For " "example, a type named :class:`T` defined in module :mod:`M` in subpackage :" "mod:`Q` in package :mod:`P` should have the :c:member:`~PyTypeObject." "tp_name` initializer ``\"P.Q.M.T\"``." msgstr "" #: ../Doc/c-api/typeobj.rst:574 msgid "" "For dynamically allocated type objects, this should just be the type name, " "and the module name explicitly stored in the type dict as the value for key " "``'__module__'``." msgstr "" #: ../Doc/c-api/typeobj.rst:578 msgid "" "For statically allocated type objects, the tp_name field should contain a " "dot. Everything before the last dot is made accessible as the :attr:" "`__module__` attribute, and everything after the last dot is made accessible " "as the :attr:`~definition.__name__` attribute." msgstr "" #: ../Doc/c-api/typeobj.rst:583 msgid "" "If no dot is present, the entire :c:member:`~PyTypeObject.tp_name` field is " "made accessible as the :attr:`~definition.__name__` attribute, and the :attr:" "`__module__` attribute is undefined (unless explicitly set in the " "dictionary, as explained above). This means your type will be impossible to " "pickle. Additionally, it will not be listed in module documentations " "created with pydoc." msgstr "" #: ../Doc/c-api/typeobj.rst:589 msgid "" "This field must not be ``NULL``. It is the only required field in :c:func:" "`PyTypeObject` (other than potentially :c:member:`~PyTypeObject." "tp_itemsize`)." msgstr "" #: ../Doc/c-api/typeobj.rst:601 msgid "" "These fields allow calculating the size in bytes of instances of the type." msgstr "" #: ../Doc/c-api/typeobj.rst:603 msgid "" "There are two kinds of types: types with fixed-length instances have a zero :" "c:member:`~PyTypeObject.tp_itemsize` field, types with variable-length " "instances have a non-zero :c:member:`~PyTypeObject.tp_itemsize` field. For " "a type with fixed-length instances, all instances have the same size, given " "in :c:member:`~PyTypeObject.tp_basicsize`." msgstr "" #: ../Doc/c-api/typeobj.rst:608 msgid "" "For a type with variable-length instances, the instances must have an :attr:" "`ob_size` field, and the instance size is :c:member:`~PyTypeObject." "tp_basicsize` plus N times :c:member:`~PyTypeObject.tp_itemsize`, where N is " "the \"length\" of the object. The value of N is typically stored in the " "instance's :attr:`ob_size` field. There are exceptions: for example, ints " "use a negative :attr:`ob_size` to indicate a negative number, and N is " "``abs(ob_size)`` there. Also, the presence of an :attr:`ob_size` field in " "the instance layout doesn't mean that the instance structure is variable-" "length (for example, the structure for the list type has fixed-length " "instances, yet those instances have a meaningful :attr:`ob_size` field)." msgstr "" #: ../Doc/c-api/typeobj.rst:619 msgid "" "The basic size includes the fields in the instance declared by the macro :c:" "macro:`PyObject_HEAD` or :c:macro:`PyObject_VAR_HEAD` (whichever is used to " "declare the instance struct) and this in turn includes the :attr:`_ob_prev` " "and :attr:`_ob_next` fields if they are present. This means that the only " "correct way to get an initializer for the :c:member:`~PyTypeObject." "tp_basicsize` is to use the ``sizeof`` operator on the struct used to " "declare the instance layout. The basic size does not include the GC header " "size." msgstr "" #: ../Doc/c-api/typeobj.rst:627 msgid "" "A note about alignment: if the variable items require a particular " "alignment, this should be taken care of by the value of :c:member:" "`~PyTypeObject.tp_basicsize`. Example: suppose a type implements an array " "of ``double``. :c:member:`~PyTypeObject.tp_itemsize` is ``sizeof(double)``. " "It is the programmer's responsibility that :c:member:`~PyTypeObject." "tp_basicsize` is a multiple of ``sizeof(double)`` (assuming this is the " "alignment requirement for ``double``)." msgstr "" #: ../Doc/c-api/typeobj.rst:634 msgid "" "For any type with variable-length instances, this field must not be ``NULL``." msgstr "" #: ../Doc/c-api/typeobj.rst:638 msgid "" "These fields are inherited separately by subtypes. If the base type has a " "non-zero :c:member:`~PyTypeObject.tp_itemsize`, it is generally not safe to " "set :c:member:`~PyTypeObject.tp_itemsize` to a different non-zero value in a " "subtype (though this depends on the implementation of the base type)." msgstr "" #: ../Doc/c-api/typeobj.rst:646 msgid "" "A pointer to the instance destructor function. This function must be " "defined unless the type guarantees that its instances will never be " "deallocated (as is the case for the singletons ``None`` and ``Ellipsis``). " "The function signature is::" msgstr "" #: ../Doc/c-api/typeobj.rst:652 msgid "" "The destructor function is called by the :c:func:`Py_DECREF` and :c:func:" "`Py_XDECREF` macros when the new reference count is zero. At this point, " "the instance is still in existence, but there are no references to it. The " "destructor function should free all references which the instance owns, free " "all memory buffers owned by the instance (using the freeing function " "corresponding to the allocation function used to allocate the buffer), and " "call the type's :c:member:`~PyTypeObject.tp_free` function. If the type is " "not subtypable (doesn't have the :const:`Py_TPFLAGS_BASETYPE` flag bit set), " "it is permissible to call the object deallocator directly instead of via :c:" "member:`~PyTypeObject.tp_free`. The object deallocator should be the one " "used to allocate the instance; this is normally :c:func:`PyObject_Del` if " "the instance was allocated using :c:func:`PyObject_New` or :c:func:" "`PyObject_VarNew`, or :c:func:`PyObject_GC_Del` if the instance was " "allocated using :c:func:`PyObject_GC_New` or :c:func:`PyObject_GC_NewVar`." msgstr "" #: ../Doc/c-api/typeobj.rst:667 msgid "" "Finally, if the type is heap allocated (:const:`Py_TPFLAGS_HEAPTYPE`), the " "deallocator should decrement the reference count for its type object after " "calling the type deallocator. In order to avoid dangling pointers, the " "recommended way to achieve this is:" msgstr "" #: ../Doc/c-api/typeobj.rst:689 msgid "" "An optional offset to a per-instance function that implements calling the " "object using the *vectorcall* protocol, a more efficient alternative of the " "simpler :c:member:`~PyTypeObject.tp_call`." msgstr "" #: ../Doc/c-api/typeobj.rst:693 msgid "" "This field is only used if the flag :const:`_Py_TPFLAGS_HAVE_VECTORCALL` is " "set. If so, this must be a positive integer containing the offset in the " "instance of a :c:type:`vectorcallfunc` pointer. The signature is the same as " "for :c:func:`_PyObject_Vectorcall`::" msgstr "" #: ../Doc/c-api/typeobj.rst:700 msgid "" "The *vectorcallfunc* pointer may be zero, in which case the instance behaves " "as if :const:`_Py_TPFLAGS_HAVE_VECTORCALL` was not set: calling the instance " "falls back to :c:member:`~PyTypeObject.tp_call`." msgstr "" #: ../Doc/c-api/typeobj.rst:704 msgid "" "Any class that sets ``_Py_TPFLAGS_HAVE_VECTORCALL`` must also set :c:member:" "`~PyTypeObject.tp_call` and make sure its behaviour is consistent with the " "*vectorcallfunc* function. This can be done by setting *tp_call* to " "``PyVectorcall_Call``:" msgstr "" #: ../Doc/c-api/typeobj.rst:711 msgid "" "Call *callable*'s *vectorcallfunc* with positional and keyword arguments " "given in a tuple and dict, respectively." msgstr "" #: ../Doc/c-api/typeobj.rst:714 msgid "" "This function is intended to be used in the ``tp_call`` slot. It does not " "fall back to ``tp_call`` and it currently does not check the " "``_Py_TPFLAGS_HAVE_VECTORCALL`` flag. To call an object, use one of the :c:" "func:`PyObject_Call ` functions instead." msgstr "" #: ../Doc/c-api/typeobj.rst:722 msgid "" "It is not recommended for :ref:`heap types ` to implement the " "vectorcall protocol. When a user sets ``__call__`` in Python code, only " "``tp_call`` is updated, possibly making it inconsistent with the vectorcall " "function." msgstr "" #: ../Doc/c-api/typeobj.rst:729 msgid "" "The semantics of the ``tp_vectorcall_offset`` slot are provisional and " "expected to be finalized in Python 3.9. If you use vectorcall, plan for " "updating your code for Python 3.9." msgstr "" #: ../Doc/c-api/typeobj.rst:735 msgid "" "This slot was used for print formatting in Python 2.x. In Python 3.0 to 3.7, " "it was reserved and named ``tp_print``." msgstr "" #: ../Doc/c-api/typeobj.rst:740 msgid "" "This field is inherited by subtypes together with :c:member:`~PyTypeObject." "tp_call`: a subtype inherits :c:member:`~PyTypeObject.tp_vectorcall_offset` " "from its base type when the subtype’s :c:member:`~PyTypeObject.tp_call` is " "``NULL``." msgstr "" #: ../Doc/c-api/typeobj.rst:745 msgid "" "Note that `heap types`_ (including subclasses defined in Python) do not " "inherit the :const:`_Py_TPFLAGS_HAVE_VECTORCALL` flag." msgstr "" #: ../Doc/c-api/typeobj.rst:751 msgid "An optional pointer to the get-attribute-string function." msgstr "" #: ../Doc/c-api/typeobj.rst:753 msgid "" "This field is deprecated. When it is defined, it should point to a function " "that acts the same as the :c:member:`~PyTypeObject.tp_getattro` function, " "but taking a C string instead of a Python string object to give the " "attribute name." msgstr "" #: ../Doc/c-api/typeobj.rst:759 ../Doc/c-api/typeobj.rst:951 msgid "Group: :attr:`tp_getattr`, :attr:`tp_getattro`" msgstr "" #: ../Doc/c-api/typeobj.rst:761 msgid "" "This field is inherited by subtypes together with :c:member:`~PyTypeObject." "tp_getattro`: a subtype inherits both :c:member:`~PyTypeObject.tp_getattr` " "and :c:member:`~PyTypeObject.tp_getattro` from its base type when the " "subtype's :c:member:`~PyTypeObject.tp_getattr` and :c:member:`~PyTypeObject." "tp_getattro` are both ``NULL``." msgstr "" #: ../Doc/c-api/typeobj.rst:768 ../Doc/c-api/typeobj.rst:964 msgid "" "An optional pointer to the function for setting and deleting attributes." msgstr "" #: ../Doc/c-api/typeobj.rst:770 msgid "" "This field is deprecated. When it is defined, it should point to a function " "that acts the same as the :c:member:`~PyTypeObject.tp_setattro` function, " "but taking a C string instead of a Python string object to give the " "attribute name." msgstr "" #: ../Doc/c-api/typeobj.rst:776 ../Doc/c-api/typeobj.rst:977 msgid "Group: :attr:`tp_setattr`, :attr:`tp_setattro`" msgstr "" #: ../Doc/c-api/typeobj.rst:778 msgid "" "This field is inherited by subtypes together with :c:member:`~PyTypeObject." "tp_setattro`: a subtype inherits both :c:member:`~PyTypeObject.tp_setattr` " "and :c:member:`~PyTypeObject.tp_setattro` from its base type when the " "subtype's :c:member:`~PyTypeObject.tp_setattr` and :c:member:`~PyTypeObject." "tp_setattro` are both ``NULL``." msgstr "" #: ../Doc/c-api/typeobj.rst:785 msgid "" "Pointer to an additional structure that contains fields relevant only to " "objects which implement :term:`awaitable` and :term:`asynchronous iterator` " "protocols at the C-level. See :ref:`async-structs` for details." msgstr "" #: ../Doc/c-api/typeobj.rst:789 msgid "Formerly known as ``tp_compare`` and ``tp_reserved``." msgstr "" #: ../Doc/c-api/typeobj.rst:794 msgid "" "The :c:member:`~PyTypeObject.tp_as_async` field is not inherited, but the " "contained fields are inherited individually." msgstr "" #: ../Doc/c-api/typeobj.rst:802 msgid "" "An optional pointer to a function that implements the built-in function :" "func:`repr`." msgstr "" #: ../Doc/c-api/typeobj.rst:805 msgid "The signature is the same as for :c:func:`PyObject_Repr`::" msgstr "" #: ../Doc/c-api/typeobj.rst:809 msgid "" "The function must return a string or a Unicode object. Ideally, this " "function should return a string that, when passed to :func:`eval`, given a " "suitable environment, returns an object with the same value. If this is not " "feasible, it should return a string starting with ``'<'`` and ending with " "``'>'`` from which both the type and the value of the object can be deduced." msgstr "" #: ../Doc/c-api/typeobj.rst:820 ../Doc/c-api/typeobj.rst:932 #: ../Doc/c-api/typeobj.rst:957 ../Doc/c-api/typeobj.rst:983 #: ../Doc/c-api/typeobj.rst:1025 ../Doc/c-api/typeobj.rst:1374 #: ../Doc/c-api/typeobj.rst:1526 ../Doc/c-api/typeobj.rst:1547 #: ../Doc/c-api/typeobj.rst:1645 ../Doc/c-api/typeobj.rst:1681 #: ../Doc/c-api/typeobj.rst:1699 ../Doc/c-api/typeobj.rst:1737 #: ../Doc/c-api/typeobj.rst:1758 ../Doc/c-api/typeobj.rst:1789 msgid "**Default:**" msgstr "" #: ../Doc/c-api/typeobj.rst:822 msgid "" "When this field is not set, a string of the form ``<%s object at %p>`` is " "returned, where ``%s`` is replaced by the type name, and ``%p`` by the " "object's memory address." msgstr "" #: ../Doc/c-api/typeobj.rst:829 msgid "" "Pointer to an additional structure that contains fields relevant only to " "objects which implement the number protocol. These fields are documented " "in :ref:`number-structs`." msgstr "" #: ../Doc/c-api/typeobj.rst:835 msgid "" "The :c:member:`~PyTypeObject.tp_as_number` field is not inherited, but the " "contained fields are inherited individually." msgstr "" #: ../Doc/c-api/typeobj.rst:841 msgid "" "Pointer to an additional structure that contains fields relevant only to " "objects which implement the sequence protocol. These fields are documented " "in :ref:`sequence-structs`." msgstr "" #: ../Doc/c-api/typeobj.rst:847 msgid "" "The :c:member:`~PyTypeObject.tp_as_sequence` field is not inherited, but the " "contained fields are inherited individually." msgstr "" #: ../Doc/c-api/typeobj.rst:853 msgid "" "Pointer to an additional structure that contains fields relevant only to " "objects which implement the mapping protocol. These fields are documented " "in :ref:`mapping-structs`." msgstr "" #: ../Doc/c-api/typeobj.rst:859 msgid "" "The :c:member:`~PyTypeObject.tp_as_mapping` field is not inherited, but the " "contained fields are inherited individually." msgstr "" #: ../Doc/c-api/typeobj.rst:867 msgid "" "An optional pointer to a function that implements the built-in function :" "func:`hash`." msgstr "" #: ../Doc/c-api/typeobj.rst:870 msgid "The signature is the same as for :c:func:`PyObject_Hash`::" msgstr "" #: ../Doc/c-api/typeobj.rst:874 msgid "" "The value ``-1`` should not be returned as a normal return value; when an " "error occurs during the computation of the hash value, the function should " "set an exception and return ``-1``." msgstr "" #: ../Doc/c-api/typeobj.rst:878 msgid "" "When this field is not set (*and* :attr:`tp_richcompare` is not set), an " "attempt to take the hash of the object raises :exc:`TypeError`. This is the " "same as setting it to :c:func:`PyObject_HashNotImplemented`." msgstr "" #: ../Doc/c-api/typeobj.rst:882 msgid "" "This field can be set explicitly to :c:func:`PyObject_HashNotImplemented` to " "block inheritance of the hash method from a parent type. This is interpreted " "as the equivalent of ``__hash__ = None`` at the Python level, causing " "``isinstance(o, collections.Hashable)`` to correctly return ``False``. Note " "that the converse is also true - setting ``__hash__ = None`` on a class at " "the Python level will result in the ``tp_hash`` slot being set to :c:func:" "`PyObject_HashNotImplemented`." msgstr "" #: ../Doc/c-api/typeobj.rst:892 ../Doc/c-api/typeobj.rst:1367 msgid "Group: :attr:`tp_hash`, :attr:`tp_richcompare`" msgstr "" #: ../Doc/c-api/typeobj.rst:894 msgid "" "This field is inherited by subtypes together with :c:member:`~PyTypeObject." "tp_richcompare`: a subtype inherits both of :c:member:`~PyTypeObject." "tp_richcompare` and :c:member:`~PyTypeObject.tp_hash`, when the subtype's :c:" "member:`~PyTypeObject.tp_richcompare` and :c:member:`~PyTypeObject.tp_hash` " "are both ``NULL``." msgstr "" #: ../Doc/c-api/typeobj.rst:902 msgid "" "An optional pointer to a function that implements calling the object. This " "should be ``NULL`` if the object is not callable. The signature is the same " "as for :c:func:`PyObject_Call`::" msgstr "" #: ../Doc/c-api/typeobj.rst:915 msgid "" "An optional pointer to a function that implements the built-in operation :" "func:`str`. (Note that :class:`str` is a type now, and :func:`str` calls " "the constructor for that type. This constructor calls :c:func:" "`PyObject_Str` to do the actual work, and :c:func:`PyObject_Str` will call " "this handler.)" msgstr "" #: ../Doc/c-api/typeobj.rst:920 msgid "The signature is the same as for :c:func:`PyObject_Str`::" msgstr "" #: ../Doc/c-api/typeobj.rst:924 msgid "" "The function must return a string or a Unicode object. It should be a " "\"friendly\" string representation of the object, as this is the " "representation that will be used, among other things, by the :func:`print` " "function." msgstr "" #: ../Doc/c-api/typeobj.rst:934 msgid "" "When this field is not set, :c:func:`PyObject_Repr` is called to return a " "string representation." msgstr "" #: ../Doc/c-api/typeobj.rst:940 msgid "An optional pointer to the get-attribute function." msgstr "" #: ../Doc/c-api/typeobj.rst:942 msgid "The signature is the same as for :c:func:`PyObject_GetAttr`::" msgstr "" #: ../Doc/c-api/typeobj.rst:946 msgid "" "It is usually convenient to set this field to :c:func:" "`PyObject_GenericGetAttr`, which implements the normal way of looking for " "object attributes." msgstr "" #: ../Doc/c-api/typeobj.rst:953 msgid "" "This field is inherited by subtypes together with :c:member:`~PyTypeObject." "tp_getattr`: a subtype inherits both :c:member:`~PyTypeObject.tp_getattr` " "and :c:member:`~PyTypeObject.tp_getattro` from its base type when the " "subtype's :c:member:`~PyTypeObject.tp_getattr` and :c:member:`~PyTypeObject." "tp_getattro` are both ``NULL``." msgstr "" #: ../Doc/c-api/typeobj.rst:959 msgid ":c:type:`PyBaseObject_Type` uses :c:func:`PyObject_GenericGetAttr`." msgstr "" #: ../Doc/c-api/typeobj.rst:966 msgid "The signature is the same as for :c:func:`PyObject_SetAttr`::" msgstr "" #: ../Doc/c-api/typeobj.rst:970 msgid "" "In addition, setting *value* to ``NULL`` to delete an attribute must be " "supported. It is usually convenient to set this field to :c:func:" "`PyObject_GenericSetAttr`, which implements the normal way of setting object " "attributes." msgstr "" #: ../Doc/c-api/typeobj.rst:979 msgid "" "This field is inherited by subtypes together with :c:member:`~PyTypeObject." "tp_setattr`: a subtype inherits both :c:member:`~PyTypeObject.tp_setattr` " "and :c:member:`~PyTypeObject.tp_setattro` from its base type when the " "subtype's :c:member:`~PyTypeObject.tp_setattr` and :c:member:`~PyTypeObject." "tp_setattro` are both ``NULL``." msgstr "" #: ../Doc/c-api/typeobj.rst:985 msgid ":c:type:`PyBaseObject_Type` uses :c:func:`PyObject_GenericSetAttr`." msgstr "" #: ../Doc/c-api/typeobj.rst:990 msgid "" "Pointer to an additional structure that contains fields relevant only to " "objects which implement the buffer interface. These fields are documented " "in :ref:`buffer-structs`." msgstr "" #: ../Doc/c-api/typeobj.rst:996 msgid "" "The :c:member:`~PyTypeObject.tp_as_buffer` field is not inherited, but the " "contained fields are inherited individually." msgstr "" #: ../Doc/c-api/typeobj.rst:1002 msgid "" "This field is a bit mask of various flags. Some flags indicate variant " "semantics for certain situations; others are used to indicate that certain " "fields in the type object (or in the extension structures referenced via :c:" "member:`~PyTypeObject.tp_as_number`, :c:member:`~PyTypeObject." "tp_as_sequence`, :c:member:`~PyTypeObject.tp_as_mapping`, and :c:member:" "`~PyTypeObject.tp_as_buffer`) that were historically not always present are " "valid; if such a flag bit is clear, the type fields it guards must not be " "accessed and must be considered to have a zero or ``NULL`` value instead." msgstr "" #: ../Doc/c-api/typeobj.rst:1012 msgid "" "Inheritance of this field is complicated. Most flag bits are inherited " "individually, i.e. if the base type has a flag bit set, the subtype inherits " "this flag bit. The flag bits that pertain to extension structures are " "strictly inherited if the extension structure is inherited, i.e. the base " "type's value of the flag bit is copied into the subtype together with a " "pointer to the extension structure. The :const:`Py_TPFLAGS_HAVE_GC` flag " "bit is inherited together with the :c:member:`~PyTypeObject.tp_traverse` " "and :c:member:`~PyTypeObject.tp_clear` fields, i.e. if the :const:" "`Py_TPFLAGS_HAVE_GC` flag bit is clear in the subtype and the :c:member:" "`~PyTypeObject.tp_traverse` and :c:member:`~PyTypeObject.tp_clear` fields in " "the subtype exist and have ``NULL`` values." msgstr "" #: ../Doc/c-api/typeobj.rst:1027 msgid "" ":c:type:`PyBaseObject_Type` uses ``Py_TPFLAGS_DEFAULT | " "Py_TPFLAGS_BASETYPE``." msgstr "" #: ../Doc/c-api/typeobj.rst:1030 msgid "**Bit Masks:**" msgstr "" #: ../Doc/c-api/typeobj.rst:1032 msgid "" "The following bit masks are currently defined; these can be ORed together " "using the ``|`` operator to form the value of the :c:member:`~PyTypeObject." "tp_flags` field. The macro :c:func:`PyType_HasFeature` takes a type and a " "flags value, *tp* and *f*, and checks whether ``tp->tp_flags & f`` is non-" "zero." msgstr "" #: ../Doc/c-api/typeobj.rst:1039 msgid "" "This bit is set when the type object itself is allocated on the heap, for " "example, types created dynamically using :c:func:`PyType_FromSpec`. In this " "case, the :attr:`ob_type` field of its instances is considered a reference " "to the type, and the type object is INCREF'ed when a new instance is " "created, and DECREF'ed when an instance is destroyed (this does not apply to " "instances of subtypes; only the type referenced by the instance's ob_type " "gets INCREF'ed or DECREF'ed)." msgstr "" #: ../Doc/c-api/typeobj.rst:1049 ../Doc/c-api/typeobj.rst:1060 #: ../Doc/c-api/typeobj.rst:1070 ../Doc/c-api/typeobj.rst:1080 #: ../Doc/c-api/typeobj.rst:1113 msgid "???" msgstr "" #: ../Doc/c-api/typeobj.rst:1054 msgid "" "This bit is set when the type can be used as the base type of another type. " "If this bit is clear, the type cannot be subtyped (similar to a \"final\" " "class in Java)." msgstr "" #: ../Doc/c-api/typeobj.rst:1065 msgid "" "This bit is set when the type object has been fully initialized by :c:func:" "`PyType_Ready`." msgstr "" #: ../Doc/c-api/typeobj.rst:1075 msgid "" "This bit is set while :c:func:`PyType_Ready` is in the process of " "initializing the type object." msgstr "" #: ../Doc/c-api/typeobj.rst:1085 msgid "" "This bit is set when the object supports garbage collection. If this bit is " "set, instances must be created using :c:func:`PyObject_GC_New` and destroyed " "using :c:func:`PyObject_GC_Del`. More information in section :ref:" "`supporting-cycle-detection`. This bit also implies that the GC-related " "fields :c:member:`~PyTypeObject.tp_traverse` and :c:member:`~PyTypeObject." "tp_clear` are present in the type object." msgstr "" #: ../Doc/c-api/typeobj.rst:1094 ../Doc/c-api/typeobj.rst:1247 #: ../Doc/c-api/typeobj.rst:1308 msgid "" "Group: :const:`Py_TPFLAGS_HAVE_GC`, :attr:`tp_traverse`, :attr:`tp_clear`" msgstr "" #: ../Doc/c-api/typeobj.rst:1096 msgid "" "The :const:`Py_TPFLAGS_HAVE_GC` flag bit is inherited together with the :" "attr:`tp_traverse` and :attr:`tp_clear` fields, i.e. if the :const:" "`Py_TPFLAGS_HAVE_GC` flag bit is clear in the subtype and the :attr:" "`tp_traverse` and :attr:`tp_clear` fields in the subtype exist and have " "``NULL`` values." msgstr "" #: ../Doc/c-api/typeobj.rst:1106 msgid "" "This is a bitmask of all the bits that pertain to the existence of certain " "fields in the type object and its extension structures. Currently, it " "includes the following bits: :const:`Py_TPFLAGS_HAVE_STACKLESS_EXTENSION`, :" "const:`Py_TPFLAGS_HAVE_VERSION_TAG`." msgstr "" #: ../Doc/c-api/typeobj.rst:1118 msgid "This bit indicates that objects behave like unbound methods." msgstr "" #: ../Doc/c-api/typeobj.rst:1120 msgid "If this flag is set for ``type(meth)``, then:" msgstr "" #: ../Doc/c-api/typeobj.rst:1122 msgid "" "``meth.__get__(obj, cls)(*args, **kwds)`` (with ``obj`` not None) must be " "equivalent to ``meth(obj, *args, **kwds)``." msgstr "" #: ../Doc/c-api/typeobj.rst:1125 msgid "" "``meth.__get__(None, cls)(*args, **kwds)`` must be equivalent to " "``meth(*args, **kwds)``." msgstr "" #: ../Doc/c-api/typeobj.rst:1128 msgid "" "This flag enables an optimization for typical method calls like ``obj." "meth()``: it avoids creating a temporary \"bound method\" object for ``obj." "meth``." msgstr "" #: ../Doc/c-api/typeobj.rst:1136 msgid "" "This flag is never inherited by heap types. For extension types, it is " "inherited whenever :c:member:`~PyTypeObject.tp_descr_get` is inherited." msgstr "" #: ../Doc/c-api/typeobj.rst:1153 msgid "" "These flags are used by functions such as :c:func:`PyLong_Check` to quickly " "determine if a type is a subclass of a built-in type; such specific checks " "are faster than a generic check, like :c:func:`PyObject_IsInstance`. Custom " "types that inherit from built-ins should have their :c:member:`~PyTypeObject." "tp_flags` set appropriately, or the code that interacts with such types will " "behave differently depending on what kind of check is used." msgstr "" #: ../Doc/c-api/typeobj.rst:1164 msgid "" "This bit is set when the :c:member:`~PyTypeObject.tp_finalize` slot is " "present in the type structure." msgstr "" #: ../Doc/c-api/typeobj.rst:1169 msgid "" "This flag isn't necessary anymore, as the interpreter assumes the :c:member:" "`~PyTypeObject.tp_finalize` slot is always present in the type structure." msgstr "" #: ../Doc/c-api/typeobj.rst:1176 msgid "" "This bit is set when the class implements the vectorcall protocol. See :c:" "member:`~PyTypeObject.tp_vectorcall_offset` for details." msgstr "" #: ../Doc/c-api/typeobj.rst:1181 msgid "" "This bit is set on *static* subtypes if ``tp_flags`` is not overridden: a " "subtype inherits ``_Py_TPFLAGS_HAVE_VECTORCALL`` from its base type when the " "subtype’s :c:member:`~PyTypeObject.tp_call` is ``NULL`` and the subtype's " "``Py_TPFLAGS_HEAPTYPE`` is not set." msgstr "" #: ../Doc/c-api/typeobj.rst:1186 msgid "`Heap types`_ do not inherit ``_Py_TPFLAGS_HAVE_VECTORCALL``." msgstr "" #: ../Doc/c-api/typeobj.rst:1190 msgid "" "This flag is provisional and expected to become public in Python 3.9, with a " "different name and, possibly, changed semantics. If you use vectorcall, plan " "for updating your code for Python 3.9." msgstr "" #: ../Doc/c-api/typeobj.rst:1199 msgid "" "An optional pointer to a NUL-terminated C string giving the docstring for " "this type object. This is exposed as the :attr:`__doc__` attribute on the " "type and instances of the type." msgstr "" #: ../Doc/c-api/typeobj.rst:1205 msgid "This field is *not* inherited by subtypes." msgstr "" #: ../Doc/c-api/typeobj.rst:1210 msgid "" "An optional pointer to a traversal function for the garbage collector. This " "is only used if the :const:`Py_TPFLAGS_HAVE_GC` flag bit is set. The " "signature is::" msgstr "" #: ../Doc/c-api/typeobj.rst:1215 ../Doc/c-api/typeobj.rst:1303 msgid "" "More information about Python's garbage collection scheme can be found in " "section :ref:`supporting-cycle-detection`." msgstr "" #: ../Doc/c-api/typeobj.rst:1218 msgid "" "The :c:member:`~PyTypeObject.tp_traverse` pointer is used by the garbage " "collector to detect reference cycles. A typical implementation of a :c:" "member:`~PyTypeObject.tp_traverse` function simply calls :c:func:`Py_VISIT` " "on each of the instance's members that are Python objects. For example, " "this is function :c:func:`local_traverse` from the :mod:`_thread` extension " "module::" msgstr "" #: ../Doc/c-api/typeobj.rst:1233 msgid "" "Note that :c:func:`Py_VISIT` is called only on those members that can " "participate in reference cycles. Although there is also a ``self->key`` " "member, it can only be ``NULL`` or a Python string and therefore cannot be " "part of a reference cycle." msgstr "" #: ../Doc/c-api/typeobj.rst:1237 msgid "" "On the other hand, even if you know a member can never be part of a cycle, " "as a debugging aid you may want to visit it anyway just so the :mod:`gc` " "module's :func:`~gc.get_referents` function will include it." msgstr "" #: ../Doc/c-api/typeobj.rst:1241 msgid "" "Note that :c:func:`Py_VISIT` requires the *visit* and *arg* parameters to :c:" "func:`local_traverse` to have these specific names; don't name them just " "anything." msgstr "" #: ../Doc/c-api/typeobj.rst:1249 msgid "" "This field is inherited by subtypes together with :c:member:`~PyTypeObject." "tp_clear` and the :const:`Py_TPFLAGS_HAVE_GC` flag bit: the flag bit, :c:" "member:`~PyTypeObject.tp_traverse`, and :c:member:`~PyTypeObject.tp_clear` " "are all inherited from the base type if they are all zero in the subtype." msgstr "" #: ../Doc/c-api/typeobj.rst:1257 msgid "" "An optional pointer to a clear function for the garbage collector. This is " "only used if the :const:`Py_TPFLAGS_HAVE_GC` flag bit is set. The signature " "is::" msgstr "" #: ../Doc/c-api/typeobj.rst:1262 msgid "" "The :c:member:`~PyTypeObject.tp_clear` member function is used to break " "reference cycles in cyclic garbage detected by the garbage collector. Taken " "together, all :c:member:`~PyTypeObject.tp_clear` functions in the system " "must combine to break all reference cycles. This is subtle, and if in any " "doubt supply a :c:member:`~PyTypeObject.tp_clear` function. For example, " "the tuple type does not implement a :c:member:`~PyTypeObject.tp_clear` " "function, because it's possible to prove that no reference cycle can be " "composed entirely of tuples. Therefore the :c:member:`~PyTypeObject." "tp_clear` functions of other types must be sufficient to break any cycle " "containing a tuple. This isn't immediately obvious, and there's rarely a " "good reason to avoid implementing :c:member:`~PyTypeObject.tp_clear`." msgstr "" #: ../Doc/c-api/typeobj.rst:1272 msgid "" "Implementations of :c:member:`~PyTypeObject.tp_clear` should drop the " "instance's references to those of its members that may be Python objects, " "and set its pointers to those members to ``NULL``, as in the following " "example::" msgstr "" #: ../Doc/c-api/typeobj.rst:1286 msgid "" "The :c:func:`Py_CLEAR` macro should be used, because clearing references is " "delicate: the reference to the contained object must not be decremented " "until after the pointer to the contained object is set to ``NULL``. This is " "because decrementing the reference count may cause the contained object to " "become trash, triggering a chain of reclamation activity that may include " "invoking arbitrary Python code (due to finalizers, or weakref callbacks, " "associated with the contained object). If it's possible for such code to " "reference *self* again, it's important that the pointer to the contained " "object be ``NULL`` at that time, so that *self* knows the contained object " "can no longer be used. The :c:func:`Py_CLEAR` macro performs the operations " "in a safe order." msgstr "" #: ../Doc/c-api/typeobj.rst:1297 msgid "" "Because the goal of :c:member:`~PyTypeObject.tp_clear` functions is to break " "reference cycles, it's not necessary to clear contained objects like Python " "strings or Python integers, which can't participate in reference cycles. On " "the other hand, it may be convenient to clear all contained Python objects, " "and write the type's :c:member:`~PyTypeObject.tp_dealloc` function to " "invoke :c:member:`~PyTypeObject.tp_clear`." msgstr "" #: ../Doc/c-api/typeobj.rst:1310 msgid "" "This field is inherited by subtypes together with :c:member:`~PyTypeObject." "tp_traverse` and the :const:`Py_TPFLAGS_HAVE_GC` flag bit: the flag bit, :c:" "member:`~PyTypeObject.tp_traverse`, and :c:member:`~PyTypeObject.tp_clear` " "are all inherited from the base type if they are all zero in the subtype." msgstr "" #: ../Doc/c-api/typeobj.rst:1318 msgid "" "An optional pointer to the rich comparison function, whose signature is::" msgstr "" #: ../Doc/c-api/typeobj.rst:1322 msgid "" "The first parameter is guaranteed to be an instance of the type that is " "defined by :c:type:`PyTypeObject`." msgstr "" #: ../Doc/c-api/typeobj.rst:1325 msgid "" "The function should return the result of the comparison (usually ``Py_True`` " "or ``Py_False``). If the comparison is undefined, it must return " "``Py_NotImplemented``, if another error occurred it must return ``NULL`` and " "set an exception condition." msgstr "" #: ../Doc/c-api/typeobj.rst:1330 msgid "" "The following constants are defined to be used as the third argument for :c:" "member:`~PyTypeObject.tp_richcompare` and for :c:func:`PyObject_RichCompare`:" msgstr "" #: ../Doc/c-api/typeobj.rst:1334 msgid "Constant" msgstr "Constante" #: ../Doc/c-api/typeobj.rst:1334 msgid "Comparison" msgstr "Comparaison" #: ../Doc/c-api/typeobj.rst:1336 msgid ":const:`Py_LT`" msgstr "" #: ../Doc/c-api/typeobj.rst:1336 msgid "``<``" msgstr "``<``" #: ../Doc/c-api/typeobj.rst:1338 msgid ":const:`Py_LE`" msgstr "" #: ../Doc/c-api/typeobj.rst:1338 msgid "``<=``" msgstr "``<=``" #: ../Doc/c-api/typeobj.rst:1340 msgid ":const:`Py_EQ`" msgstr "" #: ../Doc/c-api/typeobj.rst:1340 msgid "``==``" msgstr "``==``" #: ../Doc/c-api/typeobj.rst:1342 msgid ":const:`Py_NE`" msgstr "" #: ../Doc/c-api/typeobj.rst:1342 msgid "``!=``" msgstr "``!=``" #: ../Doc/c-api/typeobj.rst:1344 msgid ":const:`Py_GT`" msgstr "" #: ../Doc/c-api/typeobj.rst:1344 msgid "``>``" msgstr "``>``" #: ../Doc/c-api/typeobj.rst:1346 msgid ":const:`Py_GE`" msgstr "" #: ../Doc/c-api/typeobj.rst:1346 msgid "``>=``" msgstr "``>=``" #: ../Doc/c-api/typeobj.rst:1349 msgid "" "The following macro is defined to ease writing rich comparison functions:" msgstr "" #: ../Doc/c-api/typeobj.rst:1353 msgid "" "Return ``Py_True`` or ``Py_False`` from the function, depending on the " "result of a comparison. VAL_A and VAL_B must be orderable by C comparison " "operators (for example, they may be C ints or floats). The third argument " "specifies the requested operation, as for :c:func:`PyObject_RichCompare`." msgstr "" #: ../Doc/c-api/typeobj.rst:1359 msgid "The return value's reference count is properly incremented." msgstr "" #: ../Doc/c-api/typeobj.rst:1361 msgid "On error, sets an exception and returns ``NULL`` from the function." msgstr "" #: ../Doc/c-api/typeobj.rst:1369 msgid "" "This field is inherited by subtypes together with :c:member:`~PyTypeObject." "tp_hash`: a subtype inherits :c:member:`~PyTypeObject.tp_richcompare` and :c:" "member:`~PyTypeObject.tp_hash` when the subtype's :c:member:`~PyTypeObject." "tp_richcompare` and :c:member:`~PyTypeObject.tp_hash` are both ``NULL``." msgstr "" #: ../Doc/c-api/typeobj.rst:1376 msgid "" ":c:type:`PyBaseObject_Type` provides a :attr:`tp_richcompare` " "implementation, which may be inherited. However, if only :attr:`tp_hash` is " "defined, not even the inherited function is used and instances of the type " "will not be able to participate in any comparisons." msgstr "" #: ../Doc/c-api/typeobj.rst:1385 msgid "" "If the instances of this type are weakly referenceable, this field is " "greater than zero and contains the offset in the instance structure of the " "weak reference list head (ignoring the GC header, if present); this offset " "is used by :c:func:`PyObject_ClearWeakRefs` and the :c:func:`PyWeakref_\\*` " "functions. The instance structure needs to include a field of type :c:type:" "`PyObject\\*` which is initialized to ``NULL``." msgstr "" #: ../Doc/c-api/typeobj.rst:1392 msgid "" "Do not confuse this field with :c:member:`~PyTypeObject.tp_weaklist`; that " "is the list head for weak references to the type object itself." msgstr "" #: ../Doc/c-api/typeobj.rst:1397 msgid "" "This field is inherited by subtypes, but see the rules listed below. A " "subtype may override this offset; this means that the subtype uses a " "different weak reference list head than the base type. Since the list head " "is always found via :c:member:`~PyTypeObject.tp_weaklistoffset`, this should " "not be a problem." msgstr "" #: ../Doc/c-api/typeobj.rst:1402 msgid "" "When a type defined by a class statement has no :attr:`~object.__slots__` " "declaration, and none of its base types are weakly referenceable, the type " "is made weakly referenceable by adding a weak reference list head slot to " "the instance layout and setting the :c:member:`~PyTypeObject." "tp_weaklistoffset` of that slot's offset." msgstr "" #: ../Doc/c-api/typeobj.rst:1407 msgid "" "When a type's :attr:`__slots__` declaration contains a slot named :attr:" "`__weakref__`, that slot becomes the weak reference list head for instances " "of the type, and the slot's offset is stored in the type's :c:member:" "`~PyTypeObject.tp_weaklistoffset`." msgstr "" #: ../Doc/c-api/typeobj.rst:1412 msgid "" "When a type's :attr:`__slots__` declaration does not contain a slot named :" "attr:`__weakref__`, the type inherits its :c:member:`~PyTypeObject." "tp_weaklistoffset` from its base type." msgstr "" #: ../Doc/c-api/typeobj.rst:1419 msgid "" "An optional pointer to a function that returns an iterator for the object. " "Its presence normally signals that the instances of this type are iterable " "(although sequences may be iterable without this function)." msgstr "" #: ../Doc/c-api/typeobj.rst:1423 msgid "This function has the same signature as :c:func:`PyObject_GetIter`::" msgstr "" #: ../Doc/c-api/typeobj.rst:1434 msgid "" "An optional pointer to a function that returns the next item in an iterator. " "The signature is::" msgstr "" #: ../Doc/c-api/typeobj.rst:1439 msgid "" "When the iterator is exhausted, it must return ``NULL``; a :exc:" "`StopIteration` exception may or may not be set. When another error occurs, " "it must return ``NULL`` too. Its presence signals that the instances of " "this type are iterators." msgstr "" #: ../Doc/c-api/typeobj.rst:1444 msgid "" "Iterator types should also define the :c:member:`~PyTypeObject.tp_iter` " "function, and that function should return the iterator instance itself (not " "a new iterator instance)." msgstr "" #: ../Doc/c-api/typeobj.rst:1448 msgid "This function has the same signature as :c:func:`PyIter_Next`." msgstr "" #: ../Doc/c-api/typeobj.rst:1457 msgid "" "An optional pointer to a static ``NULL``-terminated array of :c:type:" "`PyMethodDef` structures, declaring regular methods of this type." msgstr "" #: ../Doc/c-api/typeobj.rst:1460 msgid "" "For each entry in the array, an entry is added to the type's dictionary " "(see :c:member:`~PyTypeObject.tp_dict` below) containing a method descriptor." msgstr "" #: ../Doc/c-api/typeobj.rst:1465 msgid "" "This field is not inherited by subtypes (methods are inherited through a " "different mechanism)." msgstr "" #: ../Doc/c-api/typeobj.rst:1471 msgid "" "An optional pointer to a static ``NULL``-terminated array of :c:type:" "`PyMemberDef` structures, declaring regular data members (fields or slots) " "of instances of this type." msgstr "" #: ../Doc/c-api/typeobj.rst:1475 msgid "" "For each entry in the array, an entry is added to the type's dictionary " "(see :c:member:`~PyTypeObject.tp_dict` below) containing a member descriptor." msgstr "" #: ../Doc/c-api/typeobj.rst:1480 msgid "" "This field is not inherited by subtypes (members are inherited through a " "different mechanism)." msgstr "" #: ../Doc/c-api/typeobj.rst:1486 msgid "" "An optional pointer to a static ``NULL``-terminated array of :c:type:" "`PyGetSetDef` structures, declaring computed attributes of instances of this " "type." msgstr "" #: ../Doc/c-api/typeobj.rst:1489 msgid "" "For each entry in the array, an entry is added to the type's dictionary " "(see :c:member:`~PyTypeObject.tp_dict` below) containing a getset descriptor." msgstr "" #: ../Doc/c-api/typeobj.rst:1494 msgid "" "This field is not inherited by subtypes (computed attributes are inherited " "through a different mechanism)." msgstr "" #: ../Doc/c-api/typeobj.rst:1500 msgid "" "An optional pointer to a base type from which type properties are " "inherited. At this level, only single inheritance is supported; multiple " "inheritance require dynamically creating a type object by calling the " "metatype." msgstr "" #: ../Doc/c-api/typeobj.rst:1508 msgid "" "Slot initialization is subject to the rules of initializing globals. C99 " "requires the initializers to be \"address constants\". Function designators " "like :c:func:`PyType_GenericNew`, with implicit conversion to a pointer, are " "valid C99 address constants." msgstr "" #: ../Doc/c-api/typeobj.rst:1513 msgid "" "However, the unary '&' operator applied to a non-static variable like :c:" "func:`PyBaseObject_Type` is not required to produce an address constant. " "Compilers may support this (gcc does), MSVC does not. Both compilers are " "strictly standard conforming in this particular behavior." msgstr "" #: ../Doc/c-api/typeobj.rst:1519 msgid "" "Consequently, :c:member:`~PyTypeObject.tp_base` should be set in the " "extension module's init function." msgstr "" #: ../Doc/c-api/typeobj.rst:1524 msgid "This field is not inherited by subtypes (obviously)." msgstr "" #: ../Doc/c-api/typeobj.rst:1528 msgid "" "This field defaults to ``&PyBaseObject_Type`` (which to Python programmers " "is known as the type :class:`object`)." msgstr "" #: ../Doc/c-api/typeobj.rst:1534 msgid "The type's dictionary is stored here by :c:func:`PyType_Ready`." msgstr "" #: ../Doc/c-api/typeobj.rst:1536 msgid "" "This field should normally be initialized to ``NULL`` before PyType_Ready is " "called; it may also be initialized to a dictionary containing initial " "attributes for the type. Once :c:func:`PyType_Ready` has initialized the " "type, extra attributes for the type may be added to this dictionary only if " "they don't correspond to overloaded operations (like :meth:`__add__`)." msgstr "" #: ../Doc/c-api/typeobj.rst:1544 msgid "" "This field is not inherited by subtypes (though the attributes defined in " "here are inherited through a different mechanism)." msgstr "" #: ../Doc/c-api/typeobj.rst:1549 msgid "" "If this field is ``NULL``, :c:func:`PyType_Ready` will assign a new " "dictionary to it." msgstr "" #: ../Doc/c-api/typeobj.rst:1554 msgid "" "It is not safe to use :c:func:`PyDict_SetItem` on or otherwise modify :c:" "member:`~PyTypeObject.tp_dict` with the dictionary C-API." msgstr "" #: ../Doc/c-api/typeobj.rst:1560 msgid "An optional pointer to a \"descriptor get\" function." msgstr "" #: ../Doc/c-api/typeobj.rst:1562 ../Doc/c-api/typeobj.rst:1578 #: ../Doc/c-api/typeobj.rst:1660 ../Doc/c-api/typeobj.rst:1690 #: ../Doc/c-api/typeobj.rst:1714 msgid "The function signature is::" msgstr "" #: ../Doc/c-api/typeobj.rst:1575 msgid "" "An optional pointer to a function for setting and deleting a descriptor's " "value." msgstr "" #: ../Doc/c-api/typeobj.rst:1582 msgid "The *value* argument is set to ``NULL`` to delete the value." msgstr "" #: ../Doc/c-api/typeobj.rst:1593 msgid "" "If the instances of this type have a dictionary containing instance " "variables, this field is non-zero and contains the offset in the instances " "of the type of the instance variable dictionary; this offset is used by :c:" "func:`PyObject_GenericGetAttr`." msgstr "" #: ../Doc/c-api/typeobj.rst:1598 msgid "" "Do not confuse this field with :c:member:`~PyTypeObject.tp_dict`; that is " "the dictionary for attributes of the type object itself." msgstr "" #: ../Doc/c-api/typeobj.rst:1601 msgid "" "If the value of this field is greater than zero, it specifies the offset " "from the start of the instance structure. If the value is less than zero, " "it specifies the offset from the *end* of the instance structure. A " "negative offset is more expensive to use, and should only be used when the " "instance structure contains a variable-length part. This is used for " "example to add an instance variable dictionary to subtypes of :class:`str` " "or :class:`tuple`. Note that the :c:member:`~PyTypeObject.tp_basicsize` " "field should account for the dictionary added to the end in that case, even " "though the dictionary is not included in the basic object layout. On a " "system with a pointer size of 4 bytes, :c:member:`~PyTypeObject." "tp_dictoffset` should be set to ``-4`` to indicate that the dictionary is at " "the very end of the structure." msgstr "" #: ../Doc/c-api/typeobj.rst:1613 msgid "" "The real dictionary offset in an instance can be computed from a negative :c:" "member:`~PyTypeObject.tp_dictoffset` as follows::" msgstr "" #: ../Doc/c-api/typeobj.rst:1620 msgid "" "where :c:member:`~PyTypeObject.tp_basicsize`, :c:member:`~PyTypeObject." "tp_itemsize` and :c:member:`~PyTypeObject.tp_dictoffset` are taken from the " "type object, and :attr:`ob_size` is taken from the instance. The absolute " "value is taken because ints use the sign of :attr:`ob_size` to store the " "sign of the number. (There's never a need to do this calculation yourself; " "it is done for you by :c:func:`_PyObject_GetDictPtr`.)" msgstr "" #: ../Doc/c-api/typeobj.rst:1628 msgid "" "This field is inherited by subtypes, but see the rules listed below. A " "subtype may override this offset; this means that the subtype instances " "store the dictionary at a difference offset than the base type. Since the " "dictionary is always found via :c:member:`~PyTypeObject.tp_dictoffset`, this " "should not be a problem." msgstr "" #: ../Doc/c-api/typeobj.rst:1633 msgid "" "When a type defined by a class statement has no :attr:`~object.__slots__` " "declaration, and none of its base types has an instance variable dictionary, " "a dictionary slot is added to the instance layout and the :c:member:" "`~PyTypeObject.tp_dictoffset` is set to that slot's offset." msgstr "" #: ../Doc/c-api/typeobj.rst:1638 msgid "" "When a type defined by a class statement has a :attr:`__slots__` " "declaration, the type inherits its :c:member:`~PyTypeObject.tp_dictoffset` " "from its base type." msgstr "" #: ../Doc/c-api/typeobj.rst:1641 msgid "" "(Adding a slot named :attr:`~object.__dict__` to the :attr:`__slots__` " "declaration does not have the expected effect, it just causes confusion. " "Maybe this should be added as a feature just like :attr:`__weakref__` " "though.)" msgstr "" #: ../Doc/c-api/typeobj.rst:1647 msgid "" "This slot has no default. For static types, if the field is ``NULL`` then " "no :attr:`__dict__` gets created for instances." msgstr "" #: ../Doc/c-api/typeobj.rst:1653 msgid "An optional pointer to an instance initialization function." msgstr "" #: ../Doc/c-api/typeobj.rst:1655 msgid "" "This function corresponds to the :meth:`__init__` method of classes. Like :" "meth:`__init__`, it is possible to create an instance without calling :meth:" "`__init__`, and it is possible to reinitialize an instance by calling its :" "meth:`__init__` method again." msgstr "" #: ../Doc/c-api/typeobj.rst:1664 msgid "" "The self argument is the instance to be initialized; the *args* and *kwds* " "arguments represent positional and keyword arguments of the call to :meth:" "`__init__`." msgstr "" #: ../Doc/c-api/typeobj.rst:1668 msgid "" "The :c:member:`~PyTypeObject.tp_init` function, if not ``NULL``, is called " "when an instance is created normally by calling its type, after the type's :" "c:member:`~PyTypeObject.tp_new` function has returned an instance of the " "type. If the :c:member:`~PyTypeObject.tp_new` function returns an instance " "of some other type that is not a subtype of the original type, no :c:member:" "`~PyTypeObject.tp_init` function is called; if :c:member:`~PyTypeObject." "tp_new` returns an instance of a subtype of the original type, the " "subtype's :c:member:`~PyTypeObject.tp_init` is called." msgstr "" #: ../Doc/c-api/typeobj.rst:1675 msgid "Returns ``0`` on success, ``-1`` and sets an exception on error." msgstr "" #: ../Doc/c-api/typeobj.rst:1683 msgid "For static types this field does not have a default." msgstr "" #: ../Doc/c-api/typeobj.rst:1688 msgid "An optional pointer to an instance allocation function." msgstr "" #: ../Doc/c-api/typeobj.rst:1696 msgid "" "This field is inherited by static subtypes, but not by dynamic subtypes " "(subtypes created by a class statement)." msgstr "" #: ../Doc/c-api/typeobj.rst:1701 msgid "" "For dynamic subtypes, this field is always set to :c:func:" "`PyType_GenericAlloc`, to force a standard heap allocation strategy." msgstr "" #: ../Doc/c-api/typeobj.rst:1705 msgid "" "For static subtypes, :c:type:`PyBaseObject_Type` uses :c:func:" "`PyType_GenericAlloc`. That is the recommended value for all statically " "defined types." msgstr "" #: ../Doc/c-api/typeobj.rst:1712 msgid "An optional pointer to an instance creation function." msgstr "" #: ../Doc/c-api/typeobj.rst:1718 msgid "" "The subtype argument is the type of the object being created; the *args* and " "*kwds* arguments represent positional and keyword arguments of the call to " "the type. Note that subtype doesn't have to equal the type whose :c:member:" "`~PyTypeObject.tp_new` function is called; it may be a subtype of that type " "(but not an unrelated type)." msgstr "" #: ../Doc/c-api/typeobj.rst:1724 msgid "" "The :c:member:`~PyTypeObject.tp_new` function should call ``subtype-" ">tp_alloc(subtype, nitems)`` to allocate space for the object, and then do " "only as much further initialization as is absolutely necessary. " "Initialization that can safely be ignored or repeated should be placed in " "the :c:member:`~PyTypeObject.tp_init` handler. A good rule of thumb is that " "for immutable types, all initialization should take place in :c:member:" "`~PyTypeObject.tp_new`, while for mutable types, most initialization should " "be deferred to :c:member:`~PyTypeObject.tp_init`." msgstr "" #: ../Doc/c-api/typeobj.rst:1734 msgid "" "This field is inherited by subtypes, except it is not inherited by static " "types whose :c:member:`~PyTypeObject.tp_base` is ``NULL`` or " "``&PyBaseObject_Type``." msgstr "" #: ../Doc/c-api/typeobj.rst:1739 msgid "" "For static types this field has no default. This means if the slot is " "defined as ``NULL``, the type cannot be called to create new instances; " "presumably there is some other way to create instances, like a factory " "function." msgstr "" #: ../Doc/c-api/typeobj.rst:1747 msgid "" "An optional pointer to an instance deallocation function. Its signature is::" msgstr "" #: ../Doc/c-api/typeobj.rst:1751 msgid "" "An initializer that is compatible with this signature is :c:func:" "`PyObject_Free`." msgstr "" #: ../Doc/c-api/typeobj.rst:1755 msgid "" "This field is inherited by static subtypes, but not by dynamic subtypes " "(subtypes created by a class statement)" msgstr "" #: ../Doc/c-api/typeobj.rst:1760 msgid "" "In dynamic subtypes, this field is set to a deallocator suitable to match :c:" "func:`PyType_GenericAlloc` and the value of the :const:`Py_TPFLAGS_HAVE_GC` " "flag bit." msgstr "" #: ../Doc/c-api/typeobj.rst:1764 msgid "For static subtypes, :c:type:`PyBaseObject_Type` uses PyObject_Del." msgstr "" #: ../Doc/c-api/typeobj.rst:1769 msgid "An optional pointer to a function called by the garbage collector." msgstr "" #: ../Doc/c-api/typeobj.rst:1771 msgid "" "The garbage collector needs to know whether a particular object is " "collectible or not. Normally, it is sufficient to look at the object's " "type's :c:member:`~PyTypeObject.tp_flags` field, and check the :const:" "`Py_TPFLAGS_HAVE_GC` flag bit. But some types have a mixture of statically " "and dynamically allocated instances, and the statically allocated instances " "are not collectible. Such types should define this function; it should " "return ``1`` for a collectible instance, and ``0`` for a non-collectible " "instance. The signature is::" msgstr "" #: ../Doc/c-api/typeobj.rst:1781 msgid "" "(The only example of this are types themselves. The metatype, :c:data:" "`PyType_Type`, defines this function to distinguish between statically and " "dynamically allocated types.)" msgstr "" #: ../Doc/c-api/typeobj.rst:1791 msgid "" "This slot has no default. If this field is ``NULL``, :const:" "`Py_TPFLAGS_HAVE_GC` is used as the functional equivalent." msgstr "" #: ../Doc/c-api/typeobj.rst:1797 msgid "Tuple of base types." msgstr "" #: ../Doc/c-api/typeobj.rst:1799 msgid "" "This is set for types created by a class statement. It should be ``NULL`` " "for statically defined types." msgstr "" #: ../Doc/c-api/typeobj.rst:1804 ../Doc/c-api/typeobj.rst:1825 #: ../Doc/c-api/typeobj.rst:1834 ../Doc/c-api/typeobj.rst:1844 #: ../Doc/c-api/typeobj.rst:1858 msgid "This field is not inherited." msgstr "" #: ../Doc/c-api/typeobj.rst:1809 msgid "" "Tuple containing the expanded set of base types, starting with the type " "itself and ending with :class:`object`, in Method Resolution Order." msgstr "" #: ../Doc/c-api/typeobj.rst:1815 msgid "" "This field is not inherited; it is calculated fresh by :c:func:" "`PyType_Ready`." msgstr "" #: ../Doc/c-api/typeobj.rst:1821 msgid "Unused. Internal use only." msgstr "" #: ../Doc/c-api/typeobj.rst:1830 msgid "List of weak references to subclasses. Internal use only." msgstr "" #: ../Doc/c-api/typeobj.rst:1839 msgid "" "Weak reference list head, for weak references to this type object. Not " "inherited. Internal use only." msgstr "" #: ../Doc/c-api/typeobj.rst:1849 msgid "" "This field is deprecated. Use :c:member:`~PyTypeObject.tp_finalize` instead." msgstr "" #: ../Doc/c-api/typeobj.rst:1854 msgid "Used to index into the method cache. Internal use only." msgstr "" #: ../Doc/c-api/typeobj.rst:1863 msgid "" "An optional pointer to an instance finalization function. Its signature is::" msgstr "" #: ../Doc/c-api/typeobj.rst:1867 msgid "" "If :c:member:`~PyTypeObject.tp_finalize` is set, the interpreter calls it " "once when finalizing an instance. It is called either from the garbage " "collector (if the instance is part of an isolated reference cycle) or just " "before the object is deallocated. Either way, it is guaranteed to be called " "before attempting to break reference cycles, ensuring that it finds the " "object in a sane state." msgstr "" #: ../Doc/c-api/typeobj.rst:1874 msgid "" ":c:member:`~PyTypeObject.tp_finalize` should not mutate the current " "exception status; therefore, a recommended way to write a non-trivial " "finalizer is::" msgstr "" #: ../Doc/c-api/typeobj.rst:1891 msgid "" "For this field to be taken into account (even through inheritance), you must " "also set the :const:`Py_TPFLAGS_HAVE_FINALIZE` flags bit." msgstr "" #: ../Doc/c-api/typeobj.rst:1900 msgid "\"Safe object finalization\" (:pep:`442`)" msgstr "" #: ../Doc/c-api/typeobj.rst:1903 msgid "" "The remaining fields are only defined if the feature test macro :const:" "`COUNT_ALLOCS` is defined, and are for internal use only. They are " "documented here for completeness. None of these fields are inherited by " "subtypes." msgstr "" #: ../Doc/c-api/typeobj.rst:1910 msgid "Number of allocations." msgstr "" #: ../Doc/c-api/typeobj.rst:1914 msgid "Number of frees." msgstr "" #: ../Doc/c-api/typeobj.rst:1918 msgid "Maximum simultaneously allocated objects." msgstr "" #: ../Doc/c-api/typeobj.rst:1922 msgid "" "Pointer to the previous type object with a non-zero :c:member:`~PyTypeObject." "tp_allocs` field." msgstr "" #: ../Doc/c-api/typeobj.rst:1926 msgid "" "Pointer to the next type object with a non-zero :c:member:`~PyTypeObject." "tp_allocs` field." msgstr "" #: ../Doc/c-api/typeobj.rst:1928 msgid "" "Also, note that, in a garbage collected Python, :c:member:`~PyTypeObject." "tp_dealloc` may be called from any Python thread, not just the thread which " "created the object (if the object becomes part of a refcount cycle, that " "cycle might be collected by a garbage collection on any thread). This is " "not a problem for Python API calls, since the thread on which tp_dealloc is " "called will own the Global Interpreter Lock (GIL). However, if the object " "being destroyed in turn destroys objects from some other C or C++ library, " "care should be taken to ensure that destroying those objects on the thread " "which called tp_dealloc will not violate any assumptions of the library." msgstr "" #: ../Doc/c-api/typeobj.rst:1942 msgid "Heap Types" msgstr "" #: ../Doc/c-api/typeobj.rst:1944 msgid "" "Traditionally, types defined in C code are *static*, that is, a static :c:" "type:`PyTypeObject` structure is defined directly in code and initialized " "using :c:func:`PyType_Ready`." msgstr "" #: ../Doc/c-api/typeobj.rst:1948 msgid "" "This results in types that are limited relative to types defined in Python:" msgstr "" #: ../Doc/c-api/typeobj.rst:1950 msgid "" "Static types are limited to one base, i.e. they cannot use multiple " "inheritance." msgstr "" #: ../Doc/c-api/typeobj.rst:1952 msgid "" "Static type objects (but not necessarily their instances) are immutable. It " "is not possible to add or modify the type object's attributes from Python." msgstr "" #: ../Doc/c-api/typeobj.rst:1954 msgid "" "Static type objects are shared across :ref:`sub-interpreters `, so they should not include any subinterpreter-" "specific state." msgstr "" #: ../Doc/c-api/typeobj.rst:1958 msgid "" "Also, since :c:type:`PyTypeObject` is not part of the :ref:`stable ABI " "`, any extension modules using static types must be compiled for a " "specific Python minor version." msgstr "" #: ../Doc/c-api/typeobj.rst:1962 msgid "" "An alternative to static types is *heap-allocated types*, or *heap types* " "for short, which correspond closely to classes created by Python's ``class`` " "statement." msgstr "" #: ../Doc/c-api/typeobj.rst:1966 msgid "" "This is done by filling a :c:type:`PyType_Spec` structure and calling :c:" "func:`PyType_FromSpecWithBases`." msgstr "" #: ../Doc/c-api/typeobj.rst:1973 msgid "Number Object Structures" msgstr "" #: ../Doc/c-api/typeobj.rst:1980 msgid "" "This structure holds pointers to the functions which an object uses to " "implement the number protocol. Each function is used by the function of " "similar name documented in the :ref:`number` section." msgstr "" #: ../Doc/c-api/typeobj.rst:1986 ../Doc/c-api/typeobj.rst:2310 msgid "Here is the structure definition::" msgstr "" #: ../Doc/c-api/typeobj.rst:2033 msgid "" "Binary and ternary functions must check the type of all their operands, and " "implement the necessary conversions (at least one of the operands is an " "instance of the defined type). If the operation is not defined for the " "given operands, binary and ternary functions must return " "``Py_NotImplemented``, if another error occurred they must return ``NULL`` " "and set an exception." msgstr "" #: ../Doc/c-api/typeobj.rst:2042 msgid "" "The :c:data:`nb_reserved` field should always be ``NULL``. It was " "previously called :c:data:`nb_long`, and was renamed in Python 3.0.1." msgstr "" #: ../Doc/c-api/typeobj.rst:2087 msgid "Mapping Object Structures" msgstr "" #: ../Doc/c-api/typeobj.rst:2094 msgid "" "This structure holds pointers to the functions which an object uses to " "implement the mapping protocol. It has three members:" msgstr "" #: ../Doc/c-api/typeobj.rst:2099 msgid "" "This function is used by :c:func:`PyMapping_Size` and :c:func:" "`PyObject_Size`, and has the same signature. This slot may be set to " "``NULL`` if the object has no defined length." msgstr "" #: ../Doc/c-api/typeobj.rst:2105 msgid "" "This function is used by :c:func:`PyObject_GetItem` and :c:func:" "`PySequence_GetSlice`, and has the same signature as :c:func:`!" "PyObject_GetItem`. This slot must be filled for the :c:func:" "`PyMapping_Check` function to return ``1``, it can be ``NULL`` otherwise." msgstr "" #: ../Doc/c-api/typeobj.rst:2113 msgid "" "This function is used by :c:func:`PyObject_SetItem`, :c:func:" "`PyObject_DelItem`, :c:func:`PyObject_SetSlice` and :c:func:" "`PyObject_DelSlice`. It has the same signature as :c:func:`!" "PyObject_SetItem`, but *v* can also be set to ``NULL`` to delete an item. " "If this slot is ``NULL``, the object does not support item assignment and " "deletion." msgstr "" #: ../Doc/c-api/typeobj.rst:2124 msgid "Sequence Object Structures" msgstr "" #: ../Doc/c-api/typeobj.rst:2131 msgid "" "This structure holds pointers to the functions which an object uses to " "implement the sequence protocol." msgstr "" #: ../Doc/c-api/typeobj.rst:2136 msgid "" "This function is used by :c:func:`PySequence_Size` and :c:func:" "`PyObject_Size`, and has the same signature. It is also used for handling " "negative indices via the :c:member:`~PySequenceMethods.sq_item` and the :c:" "member:`~PySequenceMethods.sq_ass_item` slots." msgstr "" #: ../Doc/c-api/typeobj.rst:2143 msgid "" "This function is used by :c:func:`PySequence_Concat` and has the same " "signature. It is also used by the ``+`` operator, after trying the numeric " "addition via the :c:member:`~PyNumberMethods.nb_add` slot." msgstr "" #: ../Doc/c-api/typeobj.rst:2149 msgid "" "This function is used by :c:func:`PySequence_Repeat` and has the same " "signature. It is also used by the ``*`` operator, after trying numeric " "multiplication via the :c:member:`~PyNumberMethods.nb_multiply` slot." msgstr "" #: ../Doc/c-api/typeobj.rst:2155 msgid "" "This function is used by :c:func:`PySequence_GetItem` and has the same " "signature. It is also used by :c:func:`PyObject_GetItem`, after trying the " "subscription via the :c:member:`~PyMappingMethods.mp_subscript` slot. This " "slot must be filled for the :c:func:`PySequence_Check` function to return " "``1``, it can be ``NULL`` otherwise." msgstr "" #: ../Doc/c-api/typeobj.rst:2161 msgid "" "Negative indexes are handled as follows: if the :attr:`sq_length` slot is " "filled, it is called and the sequence length is used to compute a positive " "index which is passed to :attr:`sq_item`. If :attr:`sq_length` is ``NULL``, " "the index is passed as is to the function." msgstr "" #: ../Doc/c-api/typeobj.rst:2168 msgid "" "This function is used by :c:func:`PySequence_SetItem` and has the same " "signature. It is also used by :c:func:`PyObject_SetItem` and :c:func:" "`PyObject_DelItem`, after trying the item assignment and deletion via the :c:" "member:`~PyMappingMethods.mp_ass_subscript` slot. This slot may be left to " "``NULL`` if the object does not support item assignment and deletion." msgstr "" #: ../Doc/c-api/typeobj.rst:2177 msgid "" "This function may be used by :c:func:`PySequence_Contains` and has the same " "signature. This slot may be left to ``NULL``, in this case :c:func:`!" "PySequence_Contains` simply traverses the sequence until it finds a match." msgstr "" #: ../Doc/c-api/typeobj.rst:2184 msgid "" "This function is used by :c:func:`PySequence_InPlaceConcat` and has the same " "signature. It should modify its first operand, and return it. This slot " "may be left to ``NULL``, in this case :c:func:`!PySequence_InPlaceConcat` " "will fall back to :c:func:`PySequence_Concat`. It is also used by the " "augmented assignment ``+=``, after trying numeric in-place addition via the :" "c:member:`~PyNumberMethods.nb_inplace_add` slot." msgstr "" #: ../Doc/c-api/typeobj.rst:2193 msgid "" "This function is used by :c:func:`PySequence_InPlaceRepeat` and has the same " "signature. It should modify its first operand, and return it. This slot " "may be left to ``NULL``, in this case :c:func:`!PySequence_InPlaceRepeat` " "will fall back to :c:func:`PySequence_Repeat`. It is also used by the " "augmented assignment ``*=``, after trying numeric in-place multiplication " "via the :c:member:`~PyNumberMethods.nb_inplace_multiply` slot." msgstr "" #: ../Doc/c-api/typeobj.rst:2204 msgid "Buffer Object Structures" msgstr "" #: ../Doc/c-api/typeobj.rst:2212 msgid "" "This structure holds pointers to the functions required by the :ref:`Buffer " "protocol `. The protocol defines how an exporter object can " "expose its internal data to consumer objects." msgstr "" #: ../Doc/c-api/typeobj.rst:2218 ../Doc/c-api/typeobj.rst:2267 #: ../Doc/c-api/typeobj.rst:2320 ../Doc/c-api/typeobj.rst:2331 #: ../Doc/c-api/typeobj.rst:2342 msgid "The signature of this function is::" msgstr "" #: ../Doc/c-api/typeobj.rst:2222 msgid "" "Handle a request to *exporter* to fill in *view* as specified by *flags*. " "Except for point (3), an implementation of this function MUST take these " "steps:" msgstr "" #: ../Doc/c-api/typeobj.rst:2226 msgid "" "Check if the request can be met. If not, raise :c:data:`PyExc_BufferError`, " "set :c:data:`view->obj` to ``NULL`` and return ``-1``." msgstr "" #: ../Doc/c-api/typeobj.rst:2229 msgid "Fill in the requested fields." msgstr "" #: ../Doc/c-api/typeobj.rst:2231 msgid "Increment an internal counter for the number of exports." msgstr "" #: ../Doc/c-api/typeobj.rst:2233 msgid "" "Set :c:data:`view->obj` to *exporter* and increment :c:data:`view->obj`." msgstr "" #: ../Doc/c-api/typeobj.rst:2235 msgid "Return ``0``." msgstr "" #: ../Doc/c-api/typeobj.rst:2237 msgid "" "If *exporter* is part of a chain or tree of buffer providers, two main " "schemes can be used:" msgstr "" #: ../Doc/c-api/typeobj.rst:2240 msgid "" "Re-export: Each member of the tree acts as the exporting object and sets :c:" "data:`view->obj` to a new reference to itself." msgstr "" #: ../Doc/c-api/typeobj.rst:2243 msgid "" "Redirect: The buffer request is redirected to the root object of the tree. " "Here, :c:data:`view->obj` will be a new reference to the root object." msgstr "" #: ../Doc/c-api/typeobj.rst:2247 msgid "" "The individual fields of *view* are described in section :ref:`Buffer " "structure `, the rules how an exporter must react to " "specific requests are in section :ref:`Buffer request types `." msgstr "" #: ../Doc/c-api/typeobj.rst:2252 msgid "" "All memory pointed to in the :c:type:`Py_buffer` structure belongs to the " "exporter and must remain valid until there are no consumers left. :c:member:" "`~Py_buffer.format`, :c:member:`~Py_buffer.shape`, :c:member:`~Py_buffer." "strides`, :c:member:`~Py_buffer.suboffsets` and :c:member:`~Py_buffer." "internal` are read-only for the consumer." msgstr "" #: ../Doc/c-api/typeobj.rst:2259 msgid "" ":c:func:`PyBuffer_FillInfo` provides an easy way of exposing a simple bytes " "buffer while dealing correctly with all request types." msgstr "" #: ../Doc/c-api/typeobj.rst:2262 msgid "" ":c:func:`PyObject_GetBuffer` is the interface for the consumer that wraps " "this function." msgstr "" #: ../Doc/c-api/typeobj.rst:2271 msgid "" "Handle a request to release the resources of the buffer. If no resources " "need to be released, :c:member:`PyBufferProcs.bf_releasebuffer` may be " "``NULL``. Otherwise, a standard implementation of this function will take " "these optional steps:" msgstr "" #: ../Doc/c-api/typeobj.rst:2276 msgid "Decrement an internal counter for the number of exports." msgstr "" #: ../Doc/c-api/typeobj.rst:2278 msgid "If the counter is ``0``, free all memory associated with *view*." msgstr "" #: ../Doc/c-api/typeobj.rst:2280 msgid "" "The exporter MUST use the :c:member:`~Py_buffer.internal` field to keep " "track of buffer-specific resources. This field is guaranteed to remain " "constant, while a consumer MAY pass a copy of the original buffer as the " "*view* argument." msgstr "" #: ../Doc/c-api/typeobj.rst:2286 msgid "" "This function MUST NOT decrement :c:data:`view->obj`, since that is done " "automatically in :c:func:`PyBuffer_Release` (this scheme is useful for " "breaking reference cycles)." msgstr "" #: ../Doc/c-api/typeobj.rst:2291 msgid "" ":c:func:`PyBuffer_Release` is the interface for the consumer that wraps this " "function." msgstr "" #: ../Doc/c-api/typeobj.rst:2299 msgid "Async Object Structures" msgstr "" #: ../Doc/c-api/typeobj.rst:2307 msgid "" "This structure holds pointers to the functions required to implement :term:" "`awaitable` and :term:`asynchronous iterator` objects." msgstr "" #: ../Doc/c-api/typeobj.rst:2324 msgid "" "The returned object must be an iterator, i.e. :c:func:`PyIter_Check` must " "return ``1`` for it." msgstr "" #: ../Doc/c-api/typeobj.rst:2327 msgid "" "This slot may be set to ``NULL`` if an object is not an :term:`awaitable`." msgstr "" #: ../Doc/c-api/typeobj.rst:2335 msgid "" "Must return an :term:`awaitable` object. See :meth:`__anext__` for details." msgstr "" #: ../Doc/c-api/typeobj.rst:2337 msgid "" "This slot may be set to ``NULL`` if an object does not implement " "asynchronous iteration protocol." msgstr "" #: ../Doc/c-api/typeobj.rst:2346 msgid "" "Must return an :term:`awaitable` object. See :meth:`__anext__` for details. " "This slot may be set to ``NULL``." msgstr "" #: ../Doc/c-api/typeobj.rst:2353 msgid "Slot Type typedefs" msgstr "" #: ../Doc/c-api/typeobj.rst:2357 msgid "" "The purpose of this function is to separate memory allocation from memory " "initialization. It should return a pointer to a block of memory of adequate " "length for the instance, suitably aligned, and initialized to zeros, but " "with :attr:`ob_refcnt` set to ``1`` and :attr:`ob_type` set to the type " "argument. If the type's :c:member:`~PyTypeObject.tp_itemsize` is non-zero, " "the object's :attr:`ob_size` field should be initialized to *nitems* and the " "length of the allocated memory block should be ``tp_basicsize + " "nitems*tp_itemsize``, rounded up to a multiple of ``sizeof(void*)``; " "otherwise, *nitems* is not used and the length of the block should be :c:" "member:`~PyTypeObject.tp_basicsize`." msgstr "" #: ../Doc/c-api/typeobj.rst:2367 msgid "" "This function should not do any other instance initialization, not even to " "allocate additional memory; that should be done by :c:member:`~PyTypeObject." "tp_new`." msgstr "" #: ../Doc/c-api/typeobj.rst:2374 msgid "See :c:member:`~PyTypeObject.tp_vectorcall_offset`." msgstr "" #: ../Doc/c-api/typeobj.rst:2376 msgid "" "Arguments to ``vectorcallfunc`` are the same as for :c:func:" "`_PyObject_Vectorcall`." msgstr "" #: ../Doc/c-api/typeobj.rst:2382 msgid "See :c:member:`~PyTypeObject.tp_free`." msgstr "" #: ../Doc/c-api/typeobj.rst:2386 msgid "See :c:member:`~PyTypeObject.tp_new`." msgstr "" #: ../Doc/c-api/typeobj.rst:2390 msgid "See :c:member:`~PyTypeObject.tp_init`." msgstr "" #: ../Doc/c-api/typeobj.rst:2394 msgid "See :c:member:`~PyTypeObject.tp_repr`." msgstr "" #: ../Doc/c-api/typeobj.rst:2398 ../Doc/c-api/typeobj.rst:2407 msgid "Return the value of the named attribute for the object." msgstr "" #: ../Doc/c-api/typeobj.rst:2402 ../Doc/c-api/typeobj.rst:2413 msgid "" "Set the value of the named attribute for the object. The value argument is " "set to ``NULL`` to delete the attribute." msgstr "" #: ../Doc/c-api/typeobj.rst:2409 msgid "See :c:member:`~PyTypeObject.tp_getattro`." msgstr "" #: ../Doc/c-api/typeobj.rst:2416 msgid "See :c:member:`~PyTypeObject.tp_setattro`." msgstr "" #: ../Doc/c-api/typeobj.rst:2420 msgid "See :c:member:`~PyTypeObject.tp_descrget`." msgstr "" #: ../Doc/c-api/typeobj.rst:2424 msgid "See :c:member:`~PyTypeObject.tp_descrset`." msgstr "" #: ../Doc/c-api/typeobj.rst:2428 msgid "See :c:member:`~PyTypeObject.tp_hash`." msgstr "" #: ../Doc/c-api/typeobj.rst:2432 msgid "See :c:member:`~PyTypeObject.tp_richcompare`." msgstr "" #: ../Doc/c-api/typeobj.rst:2436 msgid "See :c:member:`~PyTypeObject.tp_iter`." msgstr "" #: ../Doc/c-api/typeobj.rst:2440 msgid "See :c:member:`~PyTypeObject.tp_iternext`." msgstr "" #: ../Doc/c-api/typeobj.rst:2466 msgid "Examples" msgstr "Exemples" #: ../Doc/c-api/typeobj.rst:2468 msgid "" "The following are simple examples of Python type definitions. They include " "common usage you may encounter. Some demonstrate tricky corner cases. For " "more examples, practical info, and a tutorial, see :ref:`defining-new-types` " "and :ref:`new-types-topics`." msgstr "" #: ../Doc/c-api/typeobj.rst:2473 msgid "A basic static type::" msgstr "" #: ../Doc/c-api/typeobj.rst:2490 msgid "" "You may also find older code (especially in the CPython code base) with a " "more verbose initializer::" msgstr "" #: ../Doc/c-api/typeobj.rst:2534 msgid "A type that supports weakrefs, instance dicts, and hashing::" msgstr "" #: ../Doc/c-api/typeobj.rst:2561 msgid "" "A str subclass that cannot be subclassed and cannot be called to create " "instances (e.g. uses a separate factory func)::" msgstr "" #: ../Doc/c-api/typeobj.rst:2580 msgid "The simplest static type (with fixed-length instances)::" msgstr "" #: ../Doc/c-api/typeobj.rst:2591 msgid "The simplest static type (with variable-length instances)::" msgstr ""