sync with cpython f7567b44

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: 2025-09-08 15:25+0800\n"
+"POT-Creation-Date: 2026-01-21 00:15+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -24,8 +24,8 @@ msgstr "物件生命週期"
 msgid ""
 "This section explains how a type's slots relate to each other throughout the "
 "life of an object.  It is not intended to be a complete canonical reference "
-"for the slots; instead, refer to the slot-specific documentation "
-"in :ref:`type-structs` for details about a particular slot."
+"for the slots; instead, refer to the slot-specific documentation in :ref:"
+"`type-structs` for details about a particular slot."
 msgstr ""
 
 #: ../../c-api/lifecycle.rst:15
@@ -58,16 +58,15 @@ msgstr ":c:member:`~PyTypeObject.tp_new` 會被呼叫來建立一個新物件。
 
 #: ../../c-api/lifecycle.rst:75
 msgid ""
-":c:member:`~PyTypeObject.tp_alloc` is directly called "
-"by :c:member:`~PyTypeObject.tp_new` to allocate the memory for the new "
-"object."
+":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
 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 "
+":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 ""
 
@@ -105,19 +104,18 @@ msgstr ""
 #: ../../c-api/lifecycle.rst:100
 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."
+"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
 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 "
 "*resurrected*, preventing its pending destruction.  (Only :c:member:`!"
-"tp_finalize` is allowed to resurrect an "
-"object; :c:member:`~PyTypeObject.tp_clear` "
-"and :c:member:`~PyTypeObject.tp_dealloc` cannot without calling "
+"tp_finalize` is allowed to resurrect an object; :c:member:`~PyTypeObject."
+"tp_clear` and :c:member:`~PyTypeObject.tp_dealloc` cannot without calling "
 "into :c:member:`!tp_finalize`.)  Resurrecting an object may or may not cause "
 "the object's *finalized* mark to be removed.  Currently, Python does not "
 "remove the *finalized* mark from a resurrected object if it supports garbage "
@@ -128,38 +126,35 @@ msgstr ""
 
 #: ../../c-api/lifecycle.rst:118
 msgid ""
-":c:member:`~PyTypeObject.tp_dealloc` can optionally "
-"call :c:member:`~PyTypeObject.tp_finalize` "
-"via :c:func:`PyObject_CallFinalizerFromDealloc` if it wishes to reuse that "
-"code to help with object destruction.  This is recommended because it "
-"guarantees that :c:member:`!tp_finalize` is always called before "
-"destruction.  See the :c:member:`~PyTypeObject.tp_dealloc` documentation for "
-"example code."
+":c:member:`~PyTypeObject.tp_dealloc` can optionally call :c:member:"
+"`~PyTypeObject.tp_finalize` via :c:func:`PyObject_CallFinalizerFromDealloc` "
+"if it wishes to reuse that code to help with object destruction.  This is "
+"recommended because it guarantees that :c:member:`!tp_finalize` is always "
+"called before destruction.  See the :c:member:`~PyTypeObject.tp_dealloc` "
+"documentation for example code."
 msgstr ""
 
 #: ../../c-api/lifecycle.rst:125
 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 isolate is not detected (perhaps :func:`gc.disable` was "
-"called, or the :c:macro:`Py_TPFLAGS_HAVE_GC` flag was erroneously omitted in "
-"one of the involved types), the objects remain indefinitely uncollectable "
-"(they \"leak\").  See :data:`gc.garbage`."
+"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 "
+"isolate is not detected (perhaps :func:`gc.disable` was called, or the :c:"
+"macro:`Py_TPFLAGS_HAVE_GC` flag was erroneously omitted in one of the "
+"involved types), the objects remain indefinitely uncollectable (they "
+"\"leak\").  See :data:`gc.garbage`."
 msgstr ""
 
 #: ../../c-api/lifecycle.rst:132
 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:"
+"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
 msgid ""
-"The garbage collector occasionally "
-"calls :c:member:`~PyTypeObject.tp_traverse` to identify :term:`cyclic "
-"isolates <cyclic isolate>`."
+"The garbage collector occasionally calls :c:member:`~PyTypeObject."
+"tp_traverse` to identify :term:`cyclic isolates <cyclic isolate>`."
 msgstr ""
 
 #: ../../c-api/lifecycle.rst:139
@@ -265,9 +260,8 @@ msgid ""
 "behavior when an object referencing the destroyed object is itself "
 "destroyed.  The clearing step makes object destruction a two-phase process: "
 "first :c:member:`~PyTypeObject.tp_clear` is called to partially destroy the "
-"objects enough to detangle them from each other, "
-"then :c:member:`~PyTypeObject.tp_dealloc` is called to complete the "
-"destruction."
+"objects enough to detangle them from each other, then :c:member:"
+"`~PyTypeObject.tp_dealloc` is called to complete the destruction."
 msgstr ""
 
 #: ../../c-api/lifecycle.rst:206
@@ -277,9 +271,9 @@ msgid ""
 "contracts.  An object's finalizer is allowed to execute arbitrary Python "
 "code, and is even allowed to prevent the impending destruction by adding a "
 "reference. The finalizer is only related to destruction by call order---if "
-"it runs, it runs before destruction, which starts "
-"with :c:member:`~PyTypeObject.tp_clear` (if called) and concludes "
-"with :c:member:`~PyTypeObject.tp_dealloc`."
+"it runs, it runs before destruction, which starts with :c:member:"
+"`~PyTypeObject.tp_clear` (if called) and concludes with :c:member:"
+"`~PyTypeObject.tp_dealloc`."
 msgstr ""
 
 #: ../../c-api/lifecycle.rst:214
@@ -321,13 +315,13 @@ msgid ""
 "Without any reference cycles, an object can be simply destroyed once its "
 "last reference is deleted; the finalization and clearing steps are not "
 "necessary to safely reclaim unused objects.  However, it can be useful to "
-"automatically call :c:member:`~PyTypeObject.tp_finalize` "
-"and :c:member:`~PyTypeObject.tp_clear` before destruction anyway because "
-"type design is simplified when all objects always experience the same series "
-"of events regardless of whether they participated in a cyclic isolate.  "
-"Python currently only calls :c:member:`~PyTypeObject.tp_finalize` "
-"and :c:member:`~PyTypeObject.tp_clear` as needed to destroy a cyclic "
-"isolate; this may change in a future version."
+"automatically call :c:member:`~PyTypeObject.tp_finalize` and :c:member:"
+"`~PyTypeObject.tp_clear` before destruction anyway because type design is "
+"simplified when all objects always experience the same series of events "
+"regardless of whether they participated in a cyclic isolate.  Python "
+"currently only calls :c:member:`~PyTypeObject.tp_finalize` and :c:member:"
+"`~PyTypeObject.tp_clear` as needed to destroy a cyclic isolate; this may "
+"change in a future version."
 msgstr ""
 
 #: ../../c-api/lifecycle.rst:244
@@ -349,7 +343,7 @@ msgid ""
 "change in the future."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:262
+#: ../../c-api/lifecycle.rst:264
 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`). "
@@ -359,6 +353,6 @@ msgid ""
 "continue normally."
 msgstr ""
 
-#: ../../c-api/lifecycle.rst:271
+#: ../../c-api/lifecycle.rst:275
 msgid ":c:member:`~PyTypeObject.tp_dealloc` for example code."
 msgstr ""