sync with cpython c6f5a737

Author: github-actions[bot]

c-api/lifecycle.po

@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Python 3.14\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-01-21 00:15+0000\n"
+"POT-Creation-Date: 2026-07-06 00:35+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: Chinese - TAIWAN (https://github.com/python/python-docs-zh-"
@@ -28,8 +28,8 @@ msgid ""
 "for the slots; instead, refer to the slot-specific documentation in :ref:"
 "`type-structs` for details about a particular slot."
 msgstr ""
-"此章節說明型別的插槽如何與物件的生命週期相關聯。它並非旨在成為插槽的完整權威參考；"
-"請參閱 :ref:`type-structs` 中的插槽部分文件來了解有關於插槽的詳細資訊。"
+"此章節說明型別的插槽如何與物件的生命週期相關聯。它並非旨在成為插槽的完整權威"
+"參考；請參閱 :ref:`type-structs` 中的插槽部分文件來了解有關於插槽的詳細資訊。"
 
 #: ../../c-api/lifecycle.rst:15
 msgid "Life Events"
@@ -43,45 +43,45 @@ msgid ""
 "condition that must be true for *B* to occur after *A*."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:55 ../../c-api/lifecycle.rst:62
+#: ../../c-api/lifecycle.rst:55
 msgid "Diagram showing events in an object's life.  Explained in detail below."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:70
+#: ../../c-api/lifecycle.rst:63
 msgid "Explanation:"
 msgstr "說明："
 
-#: ../../c-api/lifecycle.rst:72
+#: ../../c-api/lifecycle.rst:65
 msgid "When a new object is constructed by calling its type:"
 msgstr "當一個新物件透過其型別來建構時："
 
-#: ../../c-api/lifecycle.rst:74
+#: ../../c-api/lifecycle.rst:67
 msgid ":c:member:`~PyTypeObject.tp_new` is called to create a new object."
 msgstr ":c:member:`~PyTypeObject.tp_new` 會被呼叫來建立一個新物件。"
 
-#: ../../c-api/lifecycle.rst:75
+#: ../../c-api/lifecycle.rst:68
 msgid ""
 ":c:member:`~PyTypeObject.tp_alloc` is directly called by :c:member:"
 "`~PyTypeObject.tp_new` to allocate the memory for the new object."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:78
+#: ../../c-api/lifecycle.rst:71
 msgid ""
 ":c:member:`~PyTypeObject.tp_init` initializes the newly created object. :c:"
 "member:`!tp_init` can be called again to re-initialize an object, if "
 "desired. The :c:member:`!tp_init` call can also be skipped entirely, for "
 "example by Python code calling :py:meth:`~object.__new__`."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:83
+#: ../../c-api/lifecycle.rst:76
 msgid "After :c:member:`!tp_init` completes, the object is ready to use."
 msgstr "在 :c:member:`!tp_init` 完成後，該物件即可使用。"
 
-#: ../../c-api/lifecycle.rst:84
+#: ../../c-api/lifecycle.rst:77
 msgid "Some time after the last reference to an object is removed:"
 msgstr "在最後一個對物件的參照被移除一段時間後："
 
-#: ../../c-api/lifecycle.rst:86
+#: ../../c-api/lifecycle.rst:79
 msgid ""
 "If an object is not marked as *finalized*, it might be finalized by marking "
 "it as *finalized* and calling its :c:member:`~PyTypeObject.tp_finalize` "
@@ -90,29 +90,29 @@ msgid ""
 "that :c:member:`~PyTypeObject.tp_finalize` is always called."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:92
+#: ../../c-api/lifecycle.rst:85
 msgid ""
 "If the object is marked as finalized, :c:member:`~PyTypeObject.tp_clear` "
 "might be called by the garbage collector to clear references held by the "
 "object.  It is *not* called when the object's reference count reaches zero."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:96
+#: ../../c-api/lifecycle.rst:89
 msgid ""
 ":c:member:`~PyTypeObject.tp_dealloc` is called to destroy the object. To "
 "avoid code duplication, :c:member:`~PyTypeObject.tp_dealloc` typically calls "
 "into :c:member:`~PyTypeObject.tp_clear` to free up the object's references."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:100
+#: ../../c-api/lifecycle.rst:93
 msgid ""
 "When :c:member:`~PyTypeObject.tp_dealloc` finishes object destruction, it "
 "directly calls :c:member:`~PyTypeObject.tp_free` (usually set to :c:func:"
 "`PyObject_Free` or :c:func:`PyObject_GC_Del` automatically as appropriate "
 "for the type) to deallocate the memory."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:105
+#: ../../c-api/lifecycle.rst:98
 msgid ""
 "The :c:member:`~PyTypeObject.tp_finalize` function is permitted to add a "
 "reference to the object if desired.  If it does, the object is "
@@ -127,7 +127,7 @@ msgid ""
 "both of these behaviors may change in the future."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:118
+#: ../../c-api/lifecycle.rst:111
 msgid ""
 ":c:member:`~PyTypeObject.tp_dealloc` can optionally call :c:member:"
 "`~PyTypeObject.tp_finalize` via :c:func:`PyObject_CallFinalizerFromDealloc` "
@@ -137,7 +137,7 @@ msgid ""
 "documentation for example code."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:125
+#: ../../c-api/lifecycle.rst:118
 msgid ""
 "If the object is a member of a :term:`cyclic isolate` and either :c:member:"
 "`~PyTypeObject.tp_clear` fails to break the reference cycle or the cyclic "
@@ -147,20 +147,20 @@ msgid ""
 "\"leak\").  See :data:`gc.garbage`."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:132
+#: ../../c-api/lifecycle.rst:125
 msgid ""
 "If the object is marked as supporting garbage collection (the :c:macro:"
 "`Py_TPFLAGS_HAVE_GC` flag is set in :c:member:`~PyTypeObject.tp_flags`), the "
 "following events are also possible:"
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:136
+#: ../../c-api/lifecycle.rst:129
 msgid ""
 "The garbage collector occasionally calls :c:member:`~PyTypeObject."
 "tp_traverse` to identify :term:`cyclic isolates <cyclic isolate>`."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:139
+#: ../../c-api/lifecycle.rst:132
 msgid ""
 "When the garbage collector discovers a :term:`cyclic isolate`, it finalizes "
 "one of the objects in the group by marking it as *finalized* and calling "
@@ -169,7 +169,7 @@ msgid ""
 "been finalized."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:144
+#: ../../c-api/lifecycle.rst:137
 msgid ""
 ":c:member:`~PyTypeObject.tp_finalize` is permitted to resurrect the object "
 "by adding a reference from outside the :term:`cyclic isolate`.  The new "
@@ -178,7 +178,7 @@ msgid ""
 "longer isolated)."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:149
+#: ../../c-api/lifecycle.rst:142
 msgid ""
 "When the garbage collector discovers a :term:`cyclic isolate` and all of the "
 "objects in the group have already been marked as *finalized*, the garbage "
@@ -188,11 +188,11 @@ msgid ""
 "all of the objects have been cleared."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:158
+#: ../../c-api/lifecycle.rst:151
 msgid "Cyclic Isolate Destruction"
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:160
+#: ../../c-api/lifecycle.rst:153
 msgid ""
 "Listed below are the stages of life of a hypothetical :term:`cyclic isolate` "
 "that continues to exist after each member object is finalized or cleared.  "
@@ -203,14 +203,14 @@ msgid ""
 "(see :c:member:`~PyTypeObject.tp_finalize`)."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:168
+#: ../../c-api/lifecycle.rst:161
 msgid ""
 "**Reachable** (not yet a cyclic isolate): All objects are in their normal, "
 "reachable state.  A reference cycle could exist, but an external reference "
 "means the objects are not yet isolated."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:171
+#: ../../c-api/lifecycle.rst:164
 msgid ""
 "**Unreachable but consistent:** The final reference from outside the cyclic "
 "group of objects has been removed, causing the objects to become isolated "
@@ -220,7 +220,7 @@ msgid ""
 "because the next run might not scan every object)."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:177
+#: ../../c-api/lifecycle.rst:170
 msgid ""
 "**Mix of finalized and not finalized:** Objects in a cyclic isolate are "
 "finalized one at a time, which means that there is a period of time when the "
@@ -231,21 +231,21 @@ msgid ""
 "an arbitrary subset of its referents."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:184
+#: ../../c-api/lifecycle.rst:177
 msgid ""
 "**All finalized:** All objects in a cyclic isolate are finalized before any "
 "of them are cleared."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:186
+#: ../../c-api/lifecycle.rst:179
 msgid ""
 "**Mix of finalized and cleared:** The objects can be cleared serially or "
 "concurrently (but with the :term:`GIL` held); either way, some will finish "
 "before others.  A finalized object must be able to tolerate the clearing of "
 "a subset of its referents.  :pep:`442` calls this stage \"cyclic trash\"."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:190
+#: ../../c-api/lifecycle.rst:183
 msgid ""
 "**Leaked:** If a cyclic isolate still exists after all objects in the group "
 "have been finalized and cleared, then the objects remain indefinitely "
@@ -255,7 +255,7 @@ msgid ""
 "required."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:197
+#: ../../c-api/lifecycle.rst:190
 msgid ""
 "If :c:member:`~PyTypeObject.tp_clear` did not exist, then Python would have "
 "no way to safely break a reference cycle.  Simply destroying an object in a "
@@ -267,7 +267,7 @@ msgid ""
 "`~PyTypeObject.tp_dealloc` is called to complete the destruction."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:206
+#: ../../c-api/lifecycle.rst:199
 msgid ""
 "Unlike clearing, finalization is not a phase of destruction.  A finalized "
 "object must still behave properly by continuing to fulfill its design "
@@ -279,7 +279,7 @@ msgid ""
 "`~PyTypeObject.tp_dealloc`."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:214
+#: ../../c-api/lifecycle.rst:207
 msgid ""
 "The finalization step is not necessary to safely reclaim the objects in a "
 "cyclic isolate, but its existence makes it easier to design types that "
@@ -291,29 +291,29 @@ msgid ""
 "only non-cleared (but potentially finalized) objects."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:223
+#: ../../c-api/lifecycle.rst:216
 msgid "To summarize the possible interactions:"
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:225
+#: ../../c-api/lifecycle.rst:218
 msgid ""
 "A non-finalized object might have references to or from non-finalized and "
 "finalized objects, but not to or from cleared objects."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:227
+#: ../../c-api/lifecycle.rst:220
 msgid ""
 "A finalized object might have references to or from non-finalized, "
 "finalized, and cleared objects."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:229
+#: ../../c-api/lifecycle.rst:222
 msgid ""
 "A cleared object might have references to or from finalized and cleared "
 "objects, but not to or from non-finalized objects."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:232
+#: ../../c-api/lifecycle.rst:225
 msgid ""
 "Without any reference cycles, an object can be simply destroyed once its "
 "last reference is deleted; the finalization and clearing steps are not "
@@ -327,15 +327,15 @@ msgid ""
 "change in a future version."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:244
+#: ../../c-api/lifecycle.rst:237
 msgid "Functions"
 msgstr "函式"
 
-#: ../../c-api/lifecycle.rst:246
+#: ../../c-api/lifecycle.rst:239
 msgid "To allocate and free memory, see :ref:`allocating-objects`."
 msgstr "要分配和釋放記憶體，請參見 :ref:`allocating-objects`。"
 
-#: ../../c-api/lifecycle.rst:251
+#: ../../c-api/lifecycle.rst:244
 msgid ""
 "Finalizes the object as described in :c:member:`~PyTypeObject.tp_finalize`. "
 "Call this function (or :c:func:`PyObject_CallFinalizerFromDealloc`) instead "
@@ -346,7 +346,7 @@ msgid ""
 "change in the future."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:264
+#: ../../c-api/lifecycle.rst:257
 msgid ""
 "Same as :c:func:`PyObject_CallFinalizer` but meant to be called at the "
 "beginning of the object's destructor (:c:member:`~PyTypeObject.tp_dealloc`). "
@@ -356,6 +356,6 @@ msgid ""
 "continue normally."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:275
+#: ../../c-api/lifecycle.rst:268
 msgid ":c:member:`~PyTypeObject.tp_dealloc` for example code."
 msgstr ""