AFPy/python-docs-fr
AFPy/python-docs-fr
Fork 80
Code Issues 6 Pull requests 10 Activity

Make merge (#1655)

Browse source
This commit is contained in:
Julien Palard 2021-06-04 13:47:25 +02:00 • committed by GitHub
commit a2b66f2e71
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
19 changed files with 1664 additions and 1586 deletions
Download patch file Download diff file Expand all files Collapse all files

68
c-api/gcsupport.po
View file

@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Python 3\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-08-24 09:01+0200\n"
"POT-Creation-Date: 2021-05-29 16:33+0200\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"
@ -60,26 +60,44 @@ msgid ""
"initialized, it must call :c:func:`PyObject_GC_Track`."
msgstr ""
#: c-api/gcsupport.rst:39
#: c-api/gcsupport.rst:37
msgid ""
"If a type adds the Py_TPFLAGS_HAVE_GC, then it *must* implement at least a :"
"c:member:`~PyTypeObject.tp_traverse` handler or explicitly use one from its "
"subclass or subclasses."
msgstr ""
#: c-api/gcsupport.rst:41
msgid ""
"When calling :c:func:`PyType_Ready` or some of the APIs that indirectly call "
"it like :c:func:`PyType_FromSpecWithBases` or :c:func:`PyType_FromSpec` the "
"interpreter will automatically populate the :c:member:`~PyTypeObject."
"tp_flags`, :c:member:`~PyTypeObject.tp_traverse` and :c:member:"
"`~PyTypeObject.tp_clear` fields if the type inherits from a class that "
"implements the garbage collector protocol and the child class does *not* "
"include the :const:`Py_TPFLAGS_HAVE_GC` flag."
msgstr ""
#: c-api/gcsupport.rst:51
msgid ""
"Analogous to :c:func:`PyObject_New` but for container objects with the :"
"const:`Py_TPFLAGS_HAVE_GC` flag set."
msgstr ""
#: c-api/gcsupport.rst:45
#: c-api/gcsupport.rst:57
msgid ""
"Analogous to :c:func:`PyObject_NewVar` but for container objects with the :"
"const:`Py_TPFLAGS_HAVE_GC` flag set."
msgstr ""
#: c-api/gcsupport.rst:51
#: c-api/gcsupport.rst:63
msgid ""
"Resize an object allocated by :c:func:`PyObject_NewVar`. Returns the "
"resized object or ``NULL`` on failure. *op* must not be tracked by the "
"collector yet."
msgstr ""
#: c-api/gcsupport.rst:57
#: c-api/gcsupport.rst:69
msgid ""
"Adds the object *op* to the set of container objects tracked by the "
"collector. The collector can run at unexpected times so objects must be "
@ -88,62 +106,62 @@ msgid ""
"usually near the end of the constructor."
msgstr ""
#: c-api/gcsupport.rst:66
#: c-api/gcsupport.rst:78
msgid ""
"Returns non-zero if the object implements the garbage collector protocol, "
"otherwise returns 0."
msgstr ""
#: c-api/gcsupport.rst:69
#: c-api/gcsupport.rst:81
msgid ""
"The object cannot be tracked by the garbage collector if this function "
"returns 0."
msgstr ""
#: c-api/gcsupport.rst:74
#: c-api/gcsupport.rst:86
msgid ""
"Returns 1 if the object type of *op* implements the GC protocol and *op* is "
"being currently tracked by the garbage collector and 0 otherwise."
msgstr ""
#: c-api/gcsupport.rst:77
#: c-api/gcsupport.rst:89
msgid "This is analogous to the Python function :func:`gc.is_tracked`."
msgstr ""
#: c-api/gcsupport.rst:84
#: c-api/gcsupport.rst:96
msgid ""
"Returns 1 if the object type of *op* implements the GC protocol and *op* has "
"been already finalized by the garbage collector and 0 otherwise."
msgstr ""
#: c-api/gcsupport.rst:87
#: c-api/gcsupport.rst:99
msgid "This is analogous to the Python function :func:`gc.is_finalized`."
msgstr ""
#: c-api/gcsupport.rst:91
#: c-api/gcsupport.rst:103
msgid ""
"Similarly, the deallocator for the object must conform to a similar pair of "
"rules:"
msgstr ""
#: c-api/gcsupport.rst:94
#: c-api/gcsupport.rst:106
msgid ""
"Before fields which refer to other containers are invalidated, :c:func:"
"`PyObject_GC_UnTrack` must be called."
msgstr ""
#: c-api/gcsupport.rst:97
#: c-api/gcsupport.rst:109
msgid ""
"The object's memory must be deallocated using :c:func:`PyObject_GC_Del`."
msgstr ""
#: c-api/gcsupport.rst:102
#: c-api/gcsupport.rst:114
msgid ""
"Releases memory allocated to an object using :c:func:`PyObject_GC_New` or :c:"
"func:`PyObject_GC_NewVar`."
msgstr ""
#: c-api/gcsupport.rst:108
#: c-api/gcsupport.rst:120
msgid ""
"Remove the object *op* from the set of container objects tracked by the "
"collector. Note that :c:func:`PyObject_GC_Track` can be called again on "
@ -153,19 +171,19 @@ msgid ""
"handler become invalid."
msgstr ""
#: c-api/gcsupport.rst:117
#: c-api/gcsupport.rst:129
msgid ""
"The :c:func:`_PyObject_GC_TRACK` and :c:func:`_PyObject_GC_UNTRACK` macros "
"have been removed from the public C API."
msgstr ""
#: c-api/gcsupport.rst:120
#: c-api/gcsupport.rst:132
msgid ""
"The :c:member:`~PyTypeObject.tp_traverse` handler accepts a function "
"parameter of this type:"
msgstr ""
#: c-api/gcsupport.rst:125
#: c-api/gcsupport.rst:137
msgid ""
"Type of the visitor function passed to the :c:member:`~PyTypeObject."
"tp_traverse` handler. The function should be called with an object to "
@ -175,13 +193,13 @@ msgid ""
"users will need to write their own visitor functions."
msgstr ""
#: c-api/gcsupport.rst:132
#: c-api/gcsupport.rst:144
msgid ""
"The :c:member:`~PyTypeObject.tp_traverse` handler must have the following "
"type:"
msgstr ""
#: c-api/gcsupport.rst:137
#: c-api/gcsupport.rst:149
msgid ""
"Traversal function for a container object. Implementations must call the "
"*visit* function for each object directly contained by *self*, with the "
@ -191,7 +209,7 @@ msgid ""
"returned immediately."
msgstr ""
#: c-api/gcsupport.rst:144
#: c-api/gcsupport.rst:156
msgid ""
"To simplify writing :c:member:`~PyTypeObject.tp_traverse` handlers, a :c:"
"func:`Py_VISIT` macro is provided. In order to use this macro, the :c:"
@ -199,20 +217,20 @@ msgid ""
"exactly *visit* and *arg*:"
msgstr ""
#: c-api/gcsupport.rst:151
#: c-api/gcsupport.rst:163
msgid ""
"If *o* is not ``NULL``, call the *visit* callback, with arguments *o* and "
"*arg*. If *visit* returns a non-zero value, then return it. Using this "
"macro, :c:member:`~PyTypeObject.tp_traverse` handlers look like::"
msgstr ""
#: c-api/gcsupport.rst:164
#: c-api/gcsupport.rst:176
msgid ""
"The :c:member:`~PyTypeObject.tp_clear` handler must be of the :c:type:"
"`inquiry` type, or ``NULL`` if the object is immutable."
msgstr ""
#: c-api/gcsupport.rst:170
#: c-api/gcsupport.rst:182
msgid ""
"Drop references that may have created reference cycles. Immutable objects "
"do not have to define this method since they can never directly create "

104
c-api/type.po
View file

@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Python 3\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-01-27 19:26+0100\n"
"POT-Creation-Date: 2021-05-29 16:33+0200\n"
"PO-Revision-Date: 2018-02-15 00:33+0100\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: FRENCH <traductions@lists.afpy.org>\n"
@ -110,7 +110,17 @@ msgid ""
"and sets an exception on error."
msgstr ""
#: c-api/type.rst:102
#: c-api/type.rst:101
msgid ""
"If some of the base classes implements the GC protocol and the provided type "
"does not include the :const:`Py_TPFLAGS_HAVE_GC` in its flags, then the GC "
"protocol will be automatically implemented from its parents. On the "
"contrary, if the type being created does include :const:`Py_TPFLAGS_HAVE_GC` "
"in its flags then it **must** implement the GC protocol itself by at least "
"implementing the :c:member:`~PyTypeObject.tp_traverse` handle."
msgstr ""
#: c-api/type.rst:111
msgid ""
"Return the function pointer stored in the given slot. If the result is "
"``NULL``, this indicates that either the slot is ``NULL``, or that the "
@ -118,28 +128,28 @@ msgid ""
"result pointer into the appropriate function type."
msgstr ""
#: c-api/type.rst:108
#: c-api/type.rst:117
msgid ""
"See :c:member:`PyType_Slot.slot` for possible values of the *slot* argument."
msgstr ""
#: c-api/type.rst:110
#: c-api/type.rst:119
msgid "An exception is raised if *type* is not a heap type."
msgstr ""
#: c-api/type.rst:116
#: c-api/type.rst:125
msgid ""
"Return the module object associated with the given type when the type was "
"created using :c:func:`PyType_FromModuleAndSpec`."
msgstr ""
#: c-api/type.rst:137
#: c-api/type.rst:146
msgid ""
"If no module is associated with the given type, sets :py:class:`TypeError` "
"and returns ``NULL``."
msgstr ""
#: c-api/type.rst:122
#: c-api/type.rst:131
msgid ""
"This function is usually used to get the module in which a method is "
"defined. Note that in such a method, ``PyType_GetModule(Py_TYPE(self))`` may "
@ -149,49 +159,49 @@ msgid ""
"defines the method."
msgstr ""
#: c-api/type.rst:133
#: c-api/type.rst:142
msgid ""
"Return the state of the module object associated with the given type. This "
"is a shortcut for calling :c:func:`PyModule_GetState()` on the result of :c:"
"func:`PyType_GetModule`."
msgstr ""
#: c-api/type.rst:140
#: c-api/type.rst:149
msgid ""
"If the *type* has an associated module but its state is ``NULL``, returns "
"``NULL`` without setting an exception."
msgstr ""
#: c-api/type.rst:147
#: c-api/type.rst:156
msgid "Creating Heap-Allocated Types"
msgstr ""
#: c-api/type.rst:149
#: c-api/type.rst:158
msgid ""
"The following functions and structs are used to create :ref:`heap types "
"<heap-types>`."
msgstr ""
#: c-api/type.rst:154
#: c-api/type.rst:163
msgid ""
"Creates and returns a heap type object from the *spec* (:const:"
"`Py_TPFLAGS_HEAPTYPE`)."
msgstr ""
#: c-api/type.rst:157
#: c-api/type.rst:166
msgid ""
"If *bases* is a tuple, the created heap type contains all types contained in "
"it as base types."
msgstr ""
#: c-api/type.rst:160
#: c-api/type.rst:169
msgid ""
"If *bases* is ``NULL``, the *Py_tp_bases* slot is used instead. If that also "
"is ``NULL``, the *Py_tp_base* slot is used instead. If that also is "
"``NULL``, the new type derives from :class:`object`."
msgstr ""
#: c-api/type.rst:164
#: c-api/type.rst:173
msgid ""
"The *module* argument can be used to record the module in which the new "
"class is defined. It must be a module object or ``NULL``. If not ``NULL``, "
@ -200,59 +210,59 @@ msgid ""
"subclasses; it must be specified for each class individually."
msgstr ""
#: c-api/type.rst:171
#: c-api/type.rst:180
msgid "This function calls :c:func:`PyType_Ready` on the new type."
msgstr ""
#: c-api/type.rst:177
#: c-api/type.rst:186
msgid "Equivalent to ``PyType_FromModuleAndSpec(NULL, spec, bases)``."
msgstr ""
#: c-api/type.rst:183
#: c-api/type.rst:192
msgid "Equivalent to ``PyType_FromSpecWithBases(spec, NULL)``."
msgstr ""
#: c-api/type.rst:187
#: c-api/type.rst:196
msgid "Structure defining a type's behavior."
msgstr ""
#: c-api/type.rst:191
#: c-api/type.rst:200
msgid "Name of the type, used to set :c:member:`PyTypeObject.tp_name`."
msgstr ""
#: c-api/type.rst:196
#: c-api/type.rst:205
msgid ""
"Size of the instance in bytes, used to set :c:member:`PyTypeObject."
"tp_basicsize` and :c:member:`PyTypeObject.tp_itemsize`."
msgstr ""
#: c-api/type.rst:202
#: c-api/type.rst:211
msgid "Type flags, used to set :c:member:`PyTypeObject.tp_flags`."
msgstr ""
#: c-api/type.rst:204
#: c-api/type.rst:213
msgid ""
"If the ``Py_TPFLAGS_HEAPTYPE`` flag is not set, :c:func:"
"`PyType_FromSpecWithBases` sets it automatically."
msgstr ""
#: c-api/type.rst:209
#: c-api/type.rst:218
msgid ""
"Array of :c:type:`PyType_Slot` structures. Terminated by the special slot "
"value ``{0, NULL}``."
msgstr ""
#: c-api/type.rst:214
#: c-api/type.rst:223
msgid ""
"Structure defining optional functionality of a type, containing a slot ID "
"and a value pointer."
msgstr ""
#: c-api/type.rst:219
#: c-api/type.rst:228
msgid "A slot ID."
msgstr ""
#: c-api/type.rst:221
#: c-api/type.rst:230
msgid ""
"Slot IDs are named like the field names of the structures :c:type:"
"`PyTypeObject`, :c:type:`PyNumberMethods`, :c:type:`PySequenceMethods`, :c:"
@ -260,97 +270,97 @@ msgid ""
"prefix. For example, use:"
msgstr ""
#: c-api/type.rst:227
#: c-api/type.rst:236
msgid "``Py_tp_dealloc`` to set :c:member:`PyTypeObject.tp_dealloc`"
msgstr ""
#: c-api/type.rst:228
#: c-api/type.rst:237
msgid "``Py_nb_add`` to set :c:member:`PyNumberMethods.nb_add`"
msgstr ""
#: c-api/type.rst:229
#: c-api/type.rst:238
msgid "``Py_sq_length`` to set :c:member:`PySequenceMethods.sq_length`"
msgstr ""
#: c-api/type.rst:231
#: c-api/type.rst:240
msgid ""
"The following fields cannot be set at all using :c:type:`PyType_Spec` and :c:"
"type:`PyType_Slot`:"
msgstr ""
#: c-api/type.rst:234
#: c-api/type.rst:243
msgid ":c:member:`~PyTypeObject.tp_dict`"
msgstr ""
#: c-api/type.rst:235
#: c-api/type.rst:244
msgid ":c:member:`~PyTypeObject.tp_mro`"
msgstr ""
#: c-api/type.rst:236
#: c-api/type.rst:245
msgid ":c:member:`~PyTypeObject.tp_cache`"
msgstr ""
#: c-api/type.rst:237
#: c-api/type.rst:246
msgid ":c:member:`~PyTypeObject.tp_subclasses`"
msgstr ""
#: c-api/type.rst:238
#: c-api/type.rst:247
msgid ":c:member:`~PyTypeObject.tp_weaklist`"
msgstr ""
#: c-api/type.rst:239
#: c-api/type.rst:248
msgid ":c:member:`~PyTypeObject.tp_vectorcall`"
msgstr ""
#: c-api/type.rst:240
#: c-api/type.rst:249
msgid ""
":c:member:`~PyTypeObject.tp_weaklistoffset` (see :ref:`PyMemberDef "
"<pymemberdef-offsets>`)"
msgstr ""
#: c-api/type.rst:242
#: c-api/type.rst:251
msgid ""
":c:member:`~PyTypeObject.tp_dictoffset` (see :ref:`PyMemberDef <pymemberdef-"
"offsets>`)"
msgstr ""
#: c-api/type.rst:244
#: c-api/type.rst:253
msgid ""
":c:member:`~PyTypeObject.tp_vectorcall_offset` (see :ref:`PyMemberDef "
"<pymemberdef-offsets>`)"
msgstr ""
#: c-api/type.rst:247
#: c-api/type.rst:256
msgid ""
"The following fields cannot be set using :c:type:`PyType_Spec` and :c:type:"
"`PyType_Slot` under the limited API:"
msgstr ""
#: c-api/type.rst:250
#: c-api/type.rst:259
msgid ":c:member:`~PyBufferProcs.bf_getbuffer`"
msgstr ""
#: c-api/type.rst:251
#: c-api/type.rst:260
msgid ":c:member:`~PyBufferProcs.bf_releasebuffer`"
msgstr ""
#: c-api/type.rst:253
#: c-api/type.rst:262
msgid ""
"Setting :c:data:`Py_tp_bases` or :c:data:`Py_tp_base` may be problematic on "
"some platforms. To avoid issues, use the *bases* argument of :py:func:"
"`PyType_FromSpecWithBases` instead."
msgstr ""
#: c-api/type.rst:260
#: c-api/type.rst:269
msgid "Slots in :c:type:`PyBufferProcs` in may be set in the unlimited API."
msgstr ""
#: c-api/type.rst:264
#: c-api/type.rst:273
msgid ""
"The desired value of the slot. In most cases, this is a pointer to a "
"function."
msgstr ""
#: c-api/type.rst:267
#: c-api/type.rst:276
msgid "May not be ``NULL``."
msgstr ""