iframe-proxy | Sunbelt Computer Software

610 lines (498 loc) · 16.6 KB
# Copyright (C) 2001-2018, Python Software Foundation
# For licence information, see README file.
"Project-Id-Version: Python 3\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-03-23 09:47+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: FRENCH <traductions@lists.afpy.org>\n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: c-api/structures.rst:6
msgid "Common Object Structures"
#: c-api/structures.rst:8
"There are a large number of structures which are used in the definition of "
"object types for Python.  This section describes these structures and how "
"they are used."
#: c-api/structures.rst:12
"All Python objects ultimately share a small number of fields at the "
"beginning of the object's representation in memory.  These are represented "
"by the :c:type:`PyObject` and :c:type:`PyVarObject` types, which are "
"defined, in turn, by the expansions of some macros also used, whether "
"directly or indirectly, in the definition of all other Python objects."
#: c-api/structures.rst:21
"All object types are extensions of this type.  This is a type which contains "
"the information Python needs to treat a pointer to an object as an object.  "
"In a normal \"release\" build, it contains only the object's reference count "
"and a pointer to the corresponding type object. Nothing is actually declared "
"to be a :c:type:`PyObject`, but every pointer to a Python object can be cast "
"to a :c:type:`PyObject*`.  Access to the members must be done by using the "
"macros :c:macro:`Py_REFCNT` and :c:macro:`Py_TYPE`."
#: c-api/structures.rst:33
"This is an extension of :c:type:`PyObject` that adds the :attr:`ob_size` "
"field.  This is only used for objects that have some notion of *length*. "
"This type does not often appear in the Python/C API. Access to the members "
"must be done by using the macros :c:macro:`Py_REFCNT`, :c:macro:`Py_TYPE`, "
"and :c:macro:`Py_SIZE`."
#: c-api/structures.rst:42
"This is a macro used when declaring new types which represent objects "
"without a varying length.  The PyObject_HEAD macro expands to::"
#: c-api/structures.rst:47
msgid "See documentation of :c:type:`PyObject` above."
#: c-api/structures.rst:52
"This is a macro used when declaring new types which represent objects with a "
"length that varies from instance to instance. The PyObject_VAR_HEAD macro "
"expands to::"
#: c-api/structures.rst:58
msgid "See documentation of :c:type:`PyVarObject` above."
#: c-api/structures.rst:63
"This macro is used to access the :attr:`ob_type` member of a Python object. "
"It expands to::"
#: c-api/structures.rst:71
"This macro is used to access the :attr:`ob_refcnt` member of a Python "
"object. It expands to::"
#: c-api/structures.rst:80
"This macro is used to access the :attr:`ob_size` member of a Python object. "
"It expands to::"
#: c-api/structures.rst:88
"This is a macro which expands to initialization values for a new :c:type:"
"`PyObject` type.  This macro expands to::"
#: c-api/structures.rst:97
"This is a macro which expands to initialization values for a new :c:type:"
"`PyVarObject` type, including the :attr:`ob_size` field. This macro expands "
#: c-api/structures.rst:107
"Type of the functions used to implement most Python callables in C. "
"Functions of this type take two :c:type:`PyObject*` parameters and return "
"one such value.  If the return value is ``NULL``, an exception shall have "
"been set.  If not ``NULL``, the return value is interpreted as the return "
"value of the function as exposed in Python.  The function must return a new "
"reference."
#: c-api/structures.rst:117
"Type of the functions used to implement Python callables in C with "
"signature :const:`METH_VARARGS | METH_KEYWORDS`."
#: c-api/structures.rst:123
"Type of the functions used to implement Python callables in C with "
"signature :const:`METH_FASTCALL`."
#: c-api/structures.rst:129
"Type of the functions used to implement Python callables in C with "
"signature :const:`METH_FASTCALL | METH_KEYWORDS`."
#: c-api/structures.rst:135
"Structure used to describe a method of an extension type.  This structure "
"has four fields:"
#: c-api/structures.rst:279 c-api/structures.rst:345
msgid "Field"
msgstr "Champ"
#: c-api/structures.rst:279 c-api/structures.rst:345
msgid "C Type"
msgstr "Type C"
#: c-api/structures.rst:279 c-api/structures.rst:345
msgid "Meaning"
msgstr "Signification"
#: c-api/structures.rst:141
msgid ":attr:`ml_name`"
msgstr ":attr:`ml_name`"
#: c-api/structures.rst:149 c-api/structures.rst:294 c-api/structures.rst:347
#: c-api/structures.rst:355
msgid "const char \\*"
#: c-api/structures.rst:141
msgid "name of the method"
#: c-api/structures.rst:143
msgid ":attr:`ml_meth`"
msgstr ":attr:`ml_meth`"
#: c-api/structures.rst:143
msgid "PyCFunction"
msgstr "PyCFunction"
#: c-api/structures.rst:143
msgid "pointer to the C implementation"
#: c-api/structures.rst:146
msgid ":attr:`ml_flags`"
msgstr ":attr:`ml_flags`"
#: c-api/structures.rst:283 c-api/structures.rst:306
msgid "int"
msgstr "*int*"
#: c-api/structures.rst:146
msgid "flag bits indicating how the call should be constructed"
#: c-api/structures.rst:149
msgid ":attr:`ml_doc`"
msgstr ":attr:`ml_doc`"
#: c-api/structures.rst:294
msgid "points to the contents of the docstring"
#: c-api/structures.rst:153
"The :attr:`ml_meth` is a C function pointer.  The functions may be of "
"different types, but they always return :c:type:`PyObject*`.  If the "
"function is not of the :c:type:`PyCFunction`, the compiler will require a "
"cast in the method table. Even though :c:type:`PyCFunction` defines the "
"first parameter as :c:type:`PyObject*`, it is common that the method "
"implementation uses the specific C type of the *self* object."
#: c-api/structures.rst:160
"The :attr:`ml_flags` field is a bitfield which can include the following "
"flags. The individual flags indicate either a calling convention or a "
"binding convention."
#: c-api/structures.rst:164
"There are four basic calling conventions for positional arguments and two of "
"them can be combined with :const:`METH_KEYWORDS` to support also keyword "
"arguments.  So there are a total of 6 calling conventions:"
#: c-api/structures.rst:170
"This is the typical calling convention, where the methods have the type :c:"
"type:`PyCFunction`. The function expects two :c:type:`PyObject*` values. The "
"first one is the *self* object for methods; for module functions, it is the "
"module object.  The second parameter (often called *args*) is a tuple object "
"representing all arguments. This parameter is typically processed using :c:"
"func:`PyArg_ParseTuple` or :c:func:`PyArg_UnpackTuple`."
#: c-api/structures.rst:180
"Methods with these flags must be of type :c:type:`PyCFunctionWithKeywords`. "
"The function expects three parameters: *self*, *args*, *kwargs* where "
"*kwargs* is a dictionary of all the keyword arguments or possibly ``NULL`` "
"if there are no keyword arguments.  The parameters are typically processed "
"using :c:func:`PyArg_ParseTupleAndKeywords`."
#: c-api/structures.rst:189
"Fast calling convention supporting only positional arguments. The methods "
"have the type :c:type:`_PyCFunctionFast`. The first parameter is *self*, the "
"second parameter is a C array of :c:type:`PyObject*` values indicating the "
"arguments and the third parameter is the number of arguments (the length of "
"the array)."
#: c-api/structures.rst:210
msgid "This is not part of the :ref:`limited API <stable>`."
#: c-api/structures.rst:202
"Extension of :const:`METH_FASTCALL` supporting also keyword arguments, with "
"methods of type :c:type:`_PyCFunctionFastWithKeywords`. Keyword arguments "
"are passed the same way as in the vectorcall protocol: there is an "
"additional fourth :c:type:`PyObject*` parameter which is a tuple "
"representing the names of the keyword arguments or possibly ``NULL`` if "
"there are no keywords.  The values of the keyword arguments are stored in "
"the *args* array, after the positional arguments."
#: c-api/structures.rst:217
"Methods without parameters don't need to check whether arguments are given "
"if they are listed with the :const:`METH_NOARGS` flag.  They need to be of "
"type :c:type:`PyCFunction`.  The first parameter is typically named *self* "
"and will hold a reference to the module or object instance.  In all cases "
"the second parameter will be ``NULL``."
#: c-api/structures.rst:226
"Methods with a single object argument can be listed with the :const:`METH_O` "
"flag, instead of invoking :c:func:`PyArg_ParseTuple` with a ``\"O\"`` "
"argument. They have the type :c:type:`PyCFunction`, with the *self* "
"parameter, and a :c:type:`PyObject*` parameter representing the single "
"argument."
#: c-api/structures.rst:232
"These two constants are not used to indicate the calling convention but the "
"binding when use with methods of classes.  These may not be used for "
"functions defined for modules.  At most one of these flags may be set for "
"any given method."
#: c-api/structures.rst:242
"The method will be passed the type object as the first parameter rather than "
"an instance of the type.  This is used to create *class methods*, similar to "
"what is created when using the :func:`classmethod` built-in function."
#: c-api/structures.rst:252
"The method will be passed ``NULL`` as the first parameter rather than an "
"instance of the type.  This is used to create *static methods*, similar to "
"what is created when using the :func:`staticmethod` built-in function."
#: c-api/structures.rst:256
"One other constant controls whether a method is loaded in place of another "
"definition with the same method name."
#: c-api/structures.rst:262
"The method will be loaded in place of existing definitions.  Without "
"*METH_COEXIST*, the default is to skip repeated definitions.  Since slot "
"wrappers are loaded before the method table, the existence of a "
"*sq_contains* slot, for example, would generate a wrapped method named :meth:"
"`__contains__` and preclude the loading of a corresponding PyCFunction with "
"the same name.  With the flag defined, the PyCFunction will be loaded in "
"place of the wrapper object and will co-exist with the slot.  This is "
"helpful because calls to PyCFunctions are optimized more than wrapper object "
#: c-api/structures.rst:275
"Structure which describes an attribute of a type which corresponds to a C "
"struct member.  Its fields are:"
#: c-api/structures.rst:281
msgid ":attr:`name`"
msgstr ":attr:`name`"
#: c-api/structures.rst:281
msgid "name of the member"
#: c-api/structures.rst:283
msgid ":attr:`!type`"
msgstr ":attr:`!type`"
#: c-api/structures.rst:283
msgid "the type of the member in the C struct"
#: c-api/structures.rst:286
msgid ":attr:`offset`"
msgstr ":attr:`offset`"
#: c-api/structures.rst:322
msgid "Py_ssize_t"
#: c-api/structures.rst:286
"the offset in bytes that the member is located on the type's object struct"
#: c-api/structures.rst:290
msgid ":attr:`flags`"
msgstr ":attr:`flags`"
#: c-api/structures.rst:290
msgid "flag bits indicating if the field should be read-only or writable"
#: c-api/structures.rst:294
msgid ":attr:`doc`"
msgstr ":attr:`doc`"
#: c-api/structures.rst:298
":attr:`!type` can be one of many ``T_`` macros corresponding to various C "
"types.  When the member is accessed in Python, it will be converted to the "
"equivalent Python type."
#: c-api/structures.rst:303
msgid "Macro name"
#: c-api/structures.rst:303
msgid "C type"
msgstr "Type C"
#: c-api/structures.rst:305
msgid "T_SHORT"
#: c-api/structures.rst:305
msgid "short"
#: c-api/structures.rst:306
msgid "T_INT"
#: c-api/structures.rst:307
msgid "T_LONG"
#: c-api/structures.rst:307
msgid "long"
#: c-api/structures.rst:308
msgid "T_FLOAT"
#: c-api/structures.rst:308
msgid "float"
msgstr "*float*"
#: c-api/structures.rst:309
msgid "T_DOUBLE"
#: c-api/structures.rst:309
msgid "double"
msgstr "double"
#: c-api/structures.rst:310
msgid "T_STRING"
#: c-api/structures.rst:311
msgid "T_OBJECT"
#: c-api/structures.rst:312
msgid "PyObject \\*"
msgstr "PyObject \\*"
#: c-api/structures.rst:312
msgid "T_OBJECT_EX"
#: c-api/structures.rst:313
msgid "T_CHAR"
#: c-api/structures.rst:314 c-api/structures.rst:319
msgid "char"
msgstr "char"
#: c-api/structures.rst:314
msgid "T_BYTE"
#: c-api/structures.rst:315
msgid "T_UBYTE"
#: c-api/structures.rst:315
msgid "unsigned char"
msgstr "``unsigned char``"
#: c-api/structures.rst:316
msgid "T_UINT"
#: c-api/structures.rst:316
msgid "unsigned int"
msgstr "``unsigned int``"
#: c-api/structures.rst:317
msgid "T_USHORT"
#: c-api/structures.rst:317
msgid "unsigned short"
msgstr "``unsigned short``"
#: c-api/structures.rst:318
msgid "T_ULONG"
#: c-api/structures.rst:318
msgid "unsigned long"
msgstr "``unsigned long``"
#: c-api/structures.rst:319
msgid "T_BOOL"
#: c-api/structures.rst:320
msgid "T_LONGLONG"
#: c-api/structures.rst:320
msgid "long long"
#: c-api/structures.rst:321
msgid "T_ULONGLONG"
#: c-api/structures.rst:321
msgid "unsigned long long"
msgstr "``unsigned long long``"
#: c-api/structures.rst:322
msgid "T_PYSSIZET"
#: c-api/structures.rst:325
":c:macro:`T_OBJECT` and :c:macro:`T_OBJECT_EX` differ in that :c:macro:"
"`T_OBJECT` returns ``None`` if the member is ``NULL`` and :c:macro:"
"`T_OBJECT_EX` raises an :exc:`AttributeError`.  Try to use :c:macro:"
"`T_OBJECT_EX` over :c:macro:`T_OBJECT` because :c:macro:`T_OBJECT_EX` "
"handles use of the :keyword:`del` statement on that attribute more correctly "
"than :c:macro:`T_OBJECT`."
#: c-api/structures.rst:332
":attr:`flags` can be ``0`` for write and read access or :c:macro:`READONLY` "
"for read-only access.  Using :c:macro:`T_STRING` for :attr:`type` implies :c:"
"macro:`READONLY`.  :c:macro:`T_STRING` data is interpreted as UTF-8. Only :c:"
"macro:`T_OBJECT` and :c:macro:`T_OBJECT_EX` members can be deleted.  (They "
"are set to ``NULL``)."
#: c-api/structures.rst:341
"Structure to define property-like access for a type. See also description of "
"the :c:member:`PyTypeObject.tp_getset` slot."
#: c-api/structures.rst:347
msgid "name"
msgstr "nom"
#: c-api/structures.rst:347
msgid "attribute name"
#: c-api/structures.rst:349
msgid "get"
#: c-api/structures.rst:349
msgid "getter"
#: c-api/structures.rst:349
msgid "C Function to get the attribute"
#: c-api/structures.rst:351
msgid "set"
#: c-api/structures.rst:351
msgid "setter"
#: c-api/structures.rst:351
"optional C function to set or delete the attribute, if omitted the attribute "
"is readonly"
#: c-api/structures.rst:355
msgid "doc"
#: c-api/structures.rst:355
msgid "optional docstring"
#: c-api/structures.rst:357
msgid "closure"
#: c-api/structures.rst:357
msgid "void \\*"
#: c-api/structures.rst:357
"optional function pointer, providing additional data for getter and setter"
#: c-api/structures.rst:362
"The ``get`` function takes one :c:type:`PyObject*` parameter (the instance) "
"and a function pointer (the associated ``closure``)::"
#: c-api/structures.rst:367
"It should return a new reference on success or ``NULL`` with a set exception "
"on failure."
#: c-api/structures.rst:370
"``set`` functions take two :c:type:`PyObject*` parameters (the instance and "
"the value to be set) and a function pointer (the associated ``closure``)::"
#: c-api/structures.rst:375
"In case the attribute should be deleted the second parameter is ``NULL``. "
"Should return ``0`` on success or ``-1`` with a set exception on failure."
Sunbelt Computer Software

PL/B Language Development and Support

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Sunbelt Computer Software

PL/B Language Development and Support

Uh oh!

Uh oh!

FilesExpand file tree

structures.po

Latest commit

History

structures.po

File metadata and controls
