[po] auto sync bot

zhsj · zhsj · commit 3702927fa3df · 2019-04-28T18:10:59.000+08:00
diff --git a/extending/extending.po b/extending/extending.po
@@ -1237,19 +1237,24 @@ msgid ""
 "this was the last reference to that object, it would free the memory "
 "associated with it, thereby invalidating ``item``."
 msgstr ""
+"既然是Python写的， :meth:`__del__` 方法可以执行任意Python代码。是否可能在 :c:func:`bug` 的 ``item``"
+" 废止引用呢，是的。假设列表传递到 :c:func:`bug` 会被 :meth:`__del__` 方法所访问，就可以执行一个语句来实现 ``del "
+"list[0]`` ，然后假设这是最后一个对对象的引用，就需要释放内存，从而使得 ``item`` 无效化。"
 
 #: ../../extending/extending.rst:1037
 msgid ""
 "The solution, once you know the source of the problem, is easy: temporarily "
 "increment the reference count.  The correct version of the function reads::"
-msgstr ""
+msgstr "解决方法是，当你知道了问题的根源，就容易了：临时增加引用计数。正确版本的函数代码如下："
 
 #: ../../extending/extending.rst:1051
 msgid ""
 "This is a true story.  An older version of Python contained variants of this"
 " bug and someone spent a considerable amount of time in a C debugger to "
 "figure out why his :meth:`__del__` methods would fail..."
 msgstr ""
+"这是个真实的故事。一个旧版本的Python包含了这个bug的变种，而一些人花费了大量时间在C调试器上去寻找为什么 :meth:`__del__` "
+"方法会失败。"
 
 #: ../../extending/extending.rst:1055
 msgid ""
@@ -1263,6 +1268,10 @@ msgid ""
 "complete. Obviously, the following function has the same problem as the "
 "previous one::"
 msgstr ""
+"这个问题的第二种情况是借用的引用涉及线程的变种。通常，Python解释器里多个线程无法进入对方的路径，因为有个全局锁保护着Python整个对象空间。但可以使用宏"
+" :c:macro:`Py_BEGIN_ALLOW_THREADS` 来临时释放这个锁，重新获取锁用 "
+":c:macro:`Py_END_ALLOW_THREADS` "
+"。这通常围绕在阻塞I/O调用外，使得其他线程可以在等待I/O期间使用处理器。显然，如下函数会跟之前那个有一样的问题："
 
 #: ../../extending/extending.rst:1078
 msgid "NULL Pointers"
@@ -1279,20 +1288,27 @@ msgid ""
 "*NULL*, there would be a lot of redundant tests and the code would run more "
 "slowly."
 msgstr ""
+"通常，函数接受对象引用作为参数，而非期待你传入 *NULL* 指针，你非这么干会导致dump core (或者之后导致core dumps) "
+"。函数返回对象引用时，返回的 *NULL* 用以指示发生了异常。 *NULL* 参数的理由在从其他函数接收时并未测试，如果每个函数都测试 *NULL* "
+"，就会导致大量的冗余测试，并使得代码运行更慢。"
 
 #: ../../extending/extending.rst:1088
 msgid ""
 "It is better to test for *NULL* only at the \"source:\" when a pointer 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:1092
 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:1096
 msgid ""
@@ -1302,19 +1318,21 @@ msgid ""
 "expected types, and this would generate redundant tests.  There are no "
 "variants with *NULL* checking."
 msgstr ""
+"用以检查对象类型的宏( ``Pytype_Check()`` )不会检查 *NULL* "
+"指针，有很多代码会多次测试一个对象是否是预期的类型，这可能产生冗余的测试。而 *NULL* 检查没有冗余。"
 
 #: ../../extending/extending.rst:1102
 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 ""
+msgstr "C函数调用机制会确保传递到C函数的参数列表 (例如 ``args`` )不会是 *NULL* ，实际上会确保总是元组 [#]_ 。"
 
 #: ../../extending/extending.rst:1106
 msgid ""
 "It is a severe error to ever let a *NULL* pointer \"escape\" to the Python "
 "user."
-msgstr ""
+msgstr "把 *NULL* 指针转义给Python用户是个严重的错误。"
 
 #: ../../extending/extending.rst:1117
 msgid "Writing Extensions in C++"
diff --git a/library/asyncio-llapi-index.po b/library/asyncio-llapi-index.po
@@ -514,88 +514,95 @@ msgstr ":meth:`loop.set_exception_handler`"
 
 #: ../../library/asyncio-llapi-index.rst:250
 msgid "Set a new exception handler."
-msgstr "设置一个新的异常处理可回调对象。"
+msgstr "设置一个新的异常处理器。"
 
 #: ../../library/asyncio-llapi-index.rst:252
 msgid ":meth:`loop.get_exception_handler`"
-msgstr ""
+msgstr ":meth:`loop.get_exception_handler`"
 
 #: ../../library/asyncio-llapi-index.rst:253
 msgid "Get the current exception handler."
-msgstr ""
+msgstr "获取当前异常处理器。"
 
 #: ../../library/asyncio-llapi-index.rst:255
 msgid ":meth:`loop.default_exception_handler`"
-msgstr ""
+msgstr ":meth:`loop.default_exception_handler`"
 
 #: ../../library/asyncio-llapi-index.rst:256
 msgid "The default exception handler implementation."
-msgstr ""
+msgstr "默认异常处理器实现。"
 
 #: ../../library/asyncio-llapi-index.rst:261
 msgid ""
 ":ref:`Using asyncio.get_event_loop() and loop.run_forever() "
 "<asyncio_example_lowlevel_helloworld>`."
 msgstr ""
+":ref:`使用 asyncio.get_event_loop() 和 loop.run_forever() "
+"<asyncio_example_lowlevel_helloworld>`."
 
 #: ../../library/asyncio-llapi-index.rst:264
 msgid ":ref:`Using loop.call_later() <asyncio_example_call_later>`."
-msgstr ""
+msgstr ":ref:`使用 loop.call_later() <asyncio_example_call_later>`."
 
 #: ../../library/asyncio-llapi-index.rst:266
 msgid ""
 "Using ``loop.create_connection()`` to implement :ref:`an echo-client "
 "<asyncio_example_tcp_echo_client_protocol>`."
 msgstr ""
+"使用 ``loop.create_connection()`` 实现 :ref:`echo客户端 "
+"<asyncio_example_tcp_echo_client_protocol>`."
 
 #: ../../library/asyncio-llapi-index.rst:269
 msgid ""
 "Using ``loop.create_connection()`` to :ref:`connect a socket "
 "<asyncio_example_create_connection>`."
 msgstr ""
+"使用``loop.create_connection()`` 去 :ref:`链接socket "
+"<asyncio_example_create_connection>`."
 
 #: ../../library/asyncio-llapi-index.rst:272
 msgid ""
 ":ref:`Using add_reader() to watch an FD for read events "
 "<asyncio_example_watch_fd>`."
-msgstr ""
+msgstr ":ref:`使用add_reader()监听FD(文件描述符)的读取事件 <asyncio_example_watch_fd>`."
 
 #: ../../library/asyncio-llapi-index.rst:275
 msgid ":ref:`Using loop.add_signal_handler() <asyncio_example_unix_signals>`."
-msgstr ""
+msgstr ":ref:`使用loop.add_signal_handler() <asyncio_example_unix_signals>`."
 
 #: ../../library/asyncio-llapi-index.rst:277
 msgid ""
 ":ref:`Using loop.subprocess_exec() <asyncio_example_subprocess_proto>`."
 msgstr ""
+":ref:`使用loop.add_signal_handler() <asyncio_example_subprocess_proto>`。"
 
 #: ../../library/asyncio-llapi-index.rst:281
 msgid "Transports"
 msgstr "传输"
 
 #: ../../library/asyncio-llapi-index.rst:283
 msgid "All transports implement the following methods:"
-msgstr ""
+msgstr "所有传输都实现以下方法:"
 
 #: ../../library/asyncio-llapi-index.rst:289
 msgid ":meth:`transport.close() <BaseTransport.close>`"
-msgstr ""
+msgstr ":meth:`transport.close() <BaseTransport.close>`"
 
 #: ../../library/asyncio-llapi-index.rst:290
 msgid "Close the transport."
-msgstr ""
+msgstr "关闭传输。"
 
 #: ../../library/asyncio-llapi-index.rst:292
 msgid ":meth:`transport.is_closing() <BaseTransport.is_closing>`"
-msgstr ""
+msgstr ":meth:`transport.is_closing() <BaseTransport.is_closing>`"
 
 #: ../../library/asyncio-llapi-index.rst:293
 msgid "Return ``True`` if the transport is closing or is closed."
-msgstr ""
+msgstr "返回 ``True`` ，如果传输正在关闭或已经关闭。。"
 
 #: ../../library/asyncio-llapi-index.rst:295
 msgid ":meth:`transport.get_extra_info() <BaseTransport.get_extra_info>`"
-msgstr ""
+msgstr ":meth:`transport.get_extra_info() <BaseTransport.get_extra_info>`"
 
 #: ../../library/asyncio-llapi-index.rst:296
 msgid "Request for information about the transport."
diff --git a/library/asyncio-protocol.po b/library/asyncio-protocol.po
@@ -9,6 +9,7 @@
 # ww song <sww4718168@gmail.com>, 2018
 # Freesand Leo <yuqinju@163.com>, 2019
 # Pan Felix <tinylambda@gmail.com>, 2019
+# MuSheng Chen <sheng.2179@gmail.com>, 2019
 # 
 #, fuzzy
 msgid ""
@@ -17,7 +18,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2019-01-01 10:14+0900\n"
 "PO-Revision-Date: 2017-02-16 17:49+0000\n"
-"Last-Translator: Pan Felix <tinylambda@gmail.com>, 2019\n"
+"Last-Translator: MuSheng Chen <sheng.2179@gmail.com>, 2019\n"
 "Language-Team: Chinese (China) (https://www.transifex.com/python-doc/teams/5390/zh_CN/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -226,7 +227,7 @@ msgstr ""
 
 #: ../../library/asyncio-protocol.rst:148
 msgid "Close the transport."
-msgstr ""
+msgstr "关闭传输。"
 
 #: ../../library/asyncio-protocol.rst:150
 msgid ""
@@ -239,7 +240,7 @@ msgstr ""
 
 #: ../../library/asyncio-protocol.rst:159
 msgid "Return ``True`` if the transport is closing or is closed."
-msgstr ""
+msgstr "返回 ``True`` ，如果传输正在关闭或已经关闭。。"
 
 #: ../../library/asyncio-protocol.rst:163
 msgid ""
diff --git a/library/multiprocessing.po b/library/multiprocessing.po
@@ -841,6 +841,9 @@ msgid ""
 "<multiprocessing.Queue.cancel_join_thread>`), then that process will not "
 "terminate until all buffered items have been flushed to the pipe."
 msgstr ""
+"正如刚才提到的，如果一个子进程将一些对象放进队列中 (并且它没有用  :meth:`JoinableQueue.cancel_join_thread "
+"<multiprocessing.Queue.cancel_join_thread>` "
+"方法)，那么这个进程在所有缓冲区的对象被刷新进管道之前，是不会终止的。"
 
 #: ../../library/multiprocessing.rst:731
 msgid ""
@@ -850,25 +853,28 @@ msgid ""
 "parent process may hang on exit when it tries to join all its non-daemonic "
 "children."
 msgstr ""
+"这意味着，除非你确定所有放入队列中的对象都已经被消费了，否则如果你试图等待这个进程，你可能会陷入死锁中。相似地，如果该子进程不是后台进程，那么父进程可能在试图等待所有非后台进程退出时挂起。"
 
 #: ../../library/multiprocessing.rst:736
 msgid ""
 "Note that a queue created using a manager does not have this issue.  See "
 ":ref:`multiprocessing-programming`."
-msgstr ""
+msgstr "注意用管理器创建的队列不存在这个问题，详见  :ref:`multiprocessing-programming` 。"
 
 #: ../../library/multiprocessing.rst:739
 msgid ""
 "For an example of the usage of queues for interprocess communication see "
 ":ref:`multiprocessing-examples`."
-msgstr ""
+msgstr "该 :ref:`multiprocessing-examples` 展示了如何使用队列实现进程间通信。"
 
 #: ../../library/multiprocessing.rst:745
 msgid ""
 "Returns a pair ``(conn1, conn2)`` of "
 ":class:`~multiprocessing.connection.Connection` objects representing the "
 "ends of a pipe."
 msgstr ""
+"返回一对 :class:`~multiprocessing.connection.Connection`对象  ``(conn1, conn2)`` ，"
+" 分别表示管道的两端。 "
 
 #: ../../library/multiprocessing.rst:749
 msgid ""
@@ -877,43 +883,50 @@ msgid ""
 " used for receiving messages and ``conn2`` can only be used for sending "
 "messages."
 msgstr ""
+"如果 *duplex* 被置为 ``True`` (默认值)，那么该管道是双向的。如果 *duplex* 被置为 ``False`` "
+"，那么该管道是单向的，即 ``conn1`` 只能用于接收消息，而  ``conn2`` 仅能用于发送消息。"
 
 #: ../../library/multiprocessing.rst:757
 msgid ""
 "Returns a process shared queue implemented using a pipe and a few "
 "locks/semaphores.  When a process first puts an item on the queue a feeder "
 "thread is started which transfers objects from a buffer into the pipe."
-msgstr ""
+msgstr "返回一个使用一个管道和少量锁和信号量实现的共享队列实例。当一个进程将一个对象放进队列中时，一个写入线程会启动并将对象从缓冲区写入管道中。"
 
 #: ../../library/multiprocessing.rst:761
 msgid ""
 "The usual :exc:`queue.Empty` and :exc:`queue.Full` exceptions from the "
 "standard library's :mod:`queue` module are raised to signal timeouts."
 msgstr ""
+"一旦超时，将抛出标准库 :mod:`queue`  模块中常见的异常:exc:`queue.Empty` 和 :exc:`queue.Full`。"
 
 #: ../../library/multiprocessing.rst:764
 msgid ""
 ":class:`Queue` implements all the methods of :class:`queue.Queue` except for"
 " :meth:`~queue.Queue.task_done` and :meth:`~queue.Queue.join`."
 msgstr ""
+"除了 :meth:`~queue.Queue.task_done` 和 :meth:`~queue.Queue.join` "
+"之外，:class:`Queue`  实现了标准库类 :class:`queue.Queue` 中所有的方法。"
 
 #: ../../library/multiprocessing.rst:769
 msgid ""
 "Return the approximate size of the queue.  Because of "
 "multithreading/multiprocessing semantics, this number is not reliable."
-msgstr ""
+msgstr "返回队列的大致长度。由于多线程或者多进程的上下文，这个数字是不可靠的。"
 
 #: ../../library/multiprocessing.rst:772
 msgid ""
 "Note that this may raise :exc:`NotImplementedError` on Unix platforms like "
 "Mac OS X where ``sem_getvalue()`` is not implemented."
 msgstr ""
+"注意，在 Unix 平台上，例如 Mac OS X ，这个方法可能会抛出 :exc:`NotImplementedError`  "
+"异常，因为该平台没有实现 ``sem_getvalue()`` 。"
 
 #: ../../library/multiprocessing.rst:777
 msgid ""
 "Return ``True`` if the queue is empty, ``False`` otherwise.  Because of "
 "multithreading/multiprocessing semantics, this is not reliable."
-msgstr ""
+msgstr "如果队列是空的，返回 ``True``  ，反之返回 ``False`` 。 同样由于多线程或多进程的存在，该状态是不可靠的。"
 
 #: ../../library/multiprocessing.rst:782
 msgid ""
