2018-07-04 09:06:45 +00:00
|
|
|
# Copyright (C) 2001-2018, Python Software Foundation
|
2018-07-04 09:08:42 +00:00
|
|
|
# For licence information, see README file.
|
2016-10-30 09:46:26 +00:00
|
|
|
#
|
|
|
|
msgid ""
|
|
|
|
msgstr ""
|
|
|
|
"Project-Id-Version: Python 3.6\n"
|
|
|
|
"Report-Msgid-Bugs-To: \n"
|
2018-06-10 09:32:30 +00:00
|
|
|
"POT-Creation-Date: 2018-06-10 11:27+0200\n"
|
2016-10-30 09:46:26 +00:00
|
|
|
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
|
|
|
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
2018-07-04 09:14:25 +00:00
|
|
|
"Language-Team: FRENCH <traductions@lists.afpy.org>\n"
|
2017-05-23 22:40:56 +00:00
|
|
|
"Language: fr\n"
|
2016-10-30 09:46:26 +00:00
|
|
|
"MIME-Version: 1.0\n"
|
|
|
|
"Content-Type: text/plain; charset=UTF-8\n"
|
|
|
|
"Content-Transfer-Encoding: 8bit\n"
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:6
|
|
|
|
msgid "Supporting Cyclic Garbage Collection"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:8
|
|
|
|
msgid ""
|
|
|
|
"Python's support for detecting and collecting garbage which involves "
|
|
|
|
"circular references requires support from object types which are \"containers"
|
|
|
|
"\" for other objects which may also be containers. Types which do not store "
|
|
|
|
"references to other objects, or which only store references to atomic types "
|
|
|
|
"(such as numbers or strings), do not need to provide any explicit support "
|
|
|
|
"for garbage collection."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:15
|
|
|
|
msgid ""
|
|
|
|
"To create a container type, the :c:member:`~PyTypeObject.tp_flags` field of "
|
|
|
|
"the type object must include the :const:`Py_TPFLAGS_HAVE_GC` and provide an "
|
|
|
|
"implementation of the :c:member:`~PyTypeObject.tp_traverse` handler. If "
|
|
|
|
"instances of the type are mutable, a :c:member:`~PyTypeObject.tp_clear` "
|
|
|
|
"implementation must also be provided."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:24
|
|
|
|
msgid ""
|
|
|
|
"Objects with a type with this flag set must conform with the rules "
|
|
|
|
"documented here. For convenience these objects will be referred to as "
|
|
|
|
"container objects."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:28
|
|
|
|
msgid "Constructors for container types must conform to two rules:"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:30
|
|
|
|
msgid ""
|
|
|
|
"The memory for the object must be allocated using :c:func:`PyObject_GC_New` "
|
|
|
|
"or :c:func:`PyObject_GC_NewVar`."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:33
|
|
|
|
msgid ""
|
|
|
|
"Once all the fields which may contain references to other containers are "
|
|
|
|
"initialized, it must call :c:func:`PyObject_GC_Track`."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:39
|
|
|
|
msgid ""
|
|
|
|
"Analogous to :c:func:`PyObject_New` but for container objects with the :"
|
|
|
|
"const:`Py_TPFLAGS_HAVE_GC` flag set."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:45
|
|
|
|
msgid ""
|
|
|
|
"Analogous to :c:func:`PyObject_NewVar` but for container objects with the :"
|
|
|
|
"const:`Py_TPFLAGS_HAVE_GC` flag set."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:51
|
|
|
|
msgid ""
|
|
|
|
"Resize an object allocated by :c:func:`PyObject_NewVar`. Returns the "
|
2018-06-10 09:32:30 +00:00
|
|
|
"resized object or *NULL* on failure. *op* must not be tracked by the "
|
|
|
|
"collector yet."
|
2016-10-30 09:46:26 +00:00
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:57
|
|
|
|
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 "
|
|
|
|
"valid while being tracked. This should be called once all the fields "
|
|
|
|
"followed by the :c:member:`~PyTypeObject.tp_traverse` handler become valid, "
|
|
|
|
"usually near the end of the constructor."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:66
|
|
|
|
msgid ""
|
|
|
|
"A macro version of :c:func:`PyObject_GC_Track`. It should not be used for "
|
|
|
|
"extension modules."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:69
|
|
|
|
msgid ""
|
|
|
|
"Similarly, the deallocator for the object must conform to a similar pair of "
|
|
|
|
"rules:"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:72
|
|
|
|
msgid ""
|
|
|
|
"Before fields which refer to other containers are invalidated, :c:func:"
|
|
|
|
"`PyObject_GC_UnTrack` must be called."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:75
|
|
|
|
msgid ""
|
|
|
|
"The object's memory must be deallocated using :c:func:`PyObject_GC_Del`."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:80
|
|
|
|
msgid ""
|
|
|
|
"Releases memory allocated to an object using :c:func:`PyObject_GC_New` or :c:"
|
|
|
|
"func:`PyObject_GC_NewVar`."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:86
|
|
|
|
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 "
|
|
|
|
"this object to add it back to the set of tracked objects. The deallocator (:"
|
|
|
|
"c:member:`~PyTypeObject.tp_dealloc` handler) should call this for the object "
|
|
|
|
"before any of the fields used by the :c:member:`~PyTypeObject.tp_traverse` "
|
|
|
|
"handler become invalid."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:95
|
|
|
|
msgid ""
|
|
|
|
"A macro version of :c:func:`PyObject_GC_UnTrack`. It should not be used for "
|
|
|
|
"extension modules."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:98
|
|
|
|
msgid ""
|
|
|
|
"The :c:member:`~PyTypeObject.tp_traverse` handler accepts a function "
|
|
|
|
"parameter of this type:"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:103
|
|
|
|
msgid ""
|
|
|
|
"Type of the visitor function passed to the :c:member:`~PyTypeObject."
|
|
|
|
"tp_traverse` handler. The function should be called with an object to "
|
|
|
|
"traverse as *object* and the third parameter to the :c:member:`~PyTypeObject."
|
|
|
|
"tp_traverse` handler as *arg*. The Python core uses several visitor "
|
|
|
|
"functions to implement cyclic garbage detection; it's not expected that "
|
|
|
|
"users will need to write their own visitor functions."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:110
|
|
|
|
msgid ""
|
|
|
|
"The :c:member:`~PyTypeObject.tp_traverse` handler must have the following "
|
|
|
|
"type:"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:115
|
|
|
|
msgid ""
|
|
|
|
"Traversal function for a container object. Implementations must call the "
|
|
|
|
"*visit* function for each object directly contained by *self*, with the "
|
|
|
|
"parameters to *visit* being the contained object and the *arg* value passed "
|
|
|
|
"to the handler. The *visit* function must not be called with a *NULL* "
|
|
|
|
"object argument. If *visit* returns a non-zero value that value should be "
|
|
|
|
"returned immediately."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:122
|
|
|
|
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:"
|
|
|
|
"member:`~PyTypeObject.tp_traverse` implementation must name its arguments "
|
|
|
|
"exactly *visit* and *arg*:"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:129
|
|
|
|
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 ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:142
|
|
|
|
msgid ""
|
|
|
|
"The :c:member:`~PyTypeObject.tp_clear` handler must be of the :c:type:"
|
|
|
|
"`inquiry` type, or *NULL* if the object is immutable."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#: ../Doc/c-api/gcsupport.rst:148
|
|
|
|
msgid ""
|
|
|
|
"Drop references that may have created reference cycles. Immutable objects "
|
|
|
|
"do not have to define this method since they can never directly create "
|
|
|
|
"reference cycles. Note that the object must still be valid after calling "
|
|
|
|
"this method (don't just call :c:func:`Py_DECREF` on a reference). The "
|
|
|
|
"collector will call this method if it detects that this object is involved "
|
|
|
|
"in a reference cycle."
|
|
|
|
msgstr ""
|