[po] auto sync

github-actions[bot] · github-actions[bot] · commit 5c1ac23f1c00 · 2020-07-09T16:10:23.000Z
diff --git a/extending/extending.po b/extending/extending.po
@@ -1304,13 +1304,17 @@ msgid ""
 "that may be ``NULL`` is received, for example, from :c:func:`malloc` or from"
 " a function that may raise an exception."
 msgstr ""
+"更好的做法是仅在“源头”上检测 ``NULL``，即在接收到一个可能为 ``NULL`` 的指针，例如来自 :c:func:`malloc` "
+"或是一个可能引发异常的函数的时候。"
 
 #: ../../extending/extending.rst:1106
 msgid ""
 "The macros :c:func:`Py_INCREF` and :c:func:`Py_DECREF` do not check for "
 "``NULL`` pointers --- however, their variants :c:func:`Py_XINCREF` and "
 ":c:func:`Py_XDECREF` do."
 msgstr ""
+":c:func:`Py_INCREF` 和 :c:func:`Py_DECREF` 等宏不会检测 ``NULL`` 指针 --- 但是，它们的变种 "
+":c:func:`Py_XINCREF` 和 :c:func:`Py_XDECREF` 则会检测。"
 
 #: ../../extending/extending.rst:1110
 msgid ""
@@ -1320,19 +1324,23 @@ msgid ""
 "expected types, and this would generate redundant tests.  There are no "
 "variants with ``NULL`` checking."
 msgstr ""
+"用于检测特定对象类型的宏 (``Pytype_Check()``) 不会检测 ``NULL`` 指针 --- "
+"同样地，有大量代码会连续调用这些宏来测试一个对象是否为几种不同预期类型之一，这将会生成冗余的测试。 不存在带有 ``NULL`` 检测的变体。"
 
 #: ../../extending/extending.rst:1116
 msgid ""
 "The C function calling mechanism guarantees that the argument list passed to"
 " C functions (``args`` in the examples) is never ``NULL`` --- in fact it "
 "guarantees that it is always a tuple [#]_."
 msgstr ""
+"C 函数调用机制会保证传给 C 函数的参数列表 (本示例中为 ``args``) 绝不会为 ``NULL`` --- 实际上它会保证其总是为一个元组 "
+"[#]_。"
 
 #: ../../extending/extending.rst:1120
 msgid ""
 "It is a severe error to ever let a ``NULL`` pointer \"escape\" to the Python"
 " user."
-msgstr ""
+msgstr "任何时候将 ``NULL`` 指针“泄露”给 Python 用户都会是个严重的错误。"
 
 #: ../../extending/extending.rst:1131
 msgid "Writing Extensions in C++"
@@ -1439,6 +1447,9 @@ msgid ""
 "of runtime type-safety; there is no feasible way to tell one unnamed Capsule"
 " from another."
 msgstr ""
+"无论你选择哪个方法，正确地为你的 Capsule 命名都很重要。 函数 :c:func:`PyCapsule_New` 接受一个名称形参 "
+"(:c:type:`const char \\*`)；允许你传入一个 ``NULL`` 作为名称，但我们强烈建议你指定一个名称。 正确地命名的 "
+"Capsule 提供了一定程序的运行时类型安全；没有可行的方式能区分两个未命名的 Capsule。"
 
 #: ../../extending/extending.rst:1200
 msgid ""
diff --git a/library/sys.po b/library/sys.po
@@ -1102,6 +1102,7 @@ msgid ""
 " one higher than you might expect, because it includes the (temporary) "
 "reference as an argument to :func:`getrefcount`."
 msgstr ""
+"返回 *object* 的引用计数。返回的计数通常比预期的多一，因为它包括了作为 :func:`getrefcount` 参数的这一次（临时）引用。"
 
 #: ../../library/sys.rst:657
 msgid ""
@@ -1110,19 +1111,21 @@ msgid ""
 "causing an overflow of the C stack and crashing Python.  It can be set by "
 ":func:`setrecursionlimit`."
 msgstr ""
+"返回当前的递归限制值，即 Python 解释器堆栈的最大深度。此限制可防止无限递归导致的 C 堆栈溢出和 Python 崩溃。该值可以通过 "
+":func:`setrecursionlimit` 设置。"
 
 #: ../../library/sys.rst:665
 msgid ""
 "Return the size of an object in bytes. The object can be any type of object."
 " All built-in objects will return correct results, but this does not have to"
 " hold true for third-party extensions as it is implementation specific."
-msgstr ""
+msgstr "返回对象的大小（以字节为单位）。该对象可以是任何类型。所有内建对象返回的结果都是正确的，但对于第三方扩展不一定正确，因为这与具体实现有关。"
 
 #: ../../library/sys.rst:670
 msgid ""
 "Only the memory consumption directly attributed to the object is accounted "
 "for, not the memory consumption of objects it refers to."
-msgstr ""
+msgstr "只计算直接分配给对象的内存消耗，不计算它所引用的对象的内存消耗。"
 
 #: ../../library/sys.rst:673
 msgid ""
