[po] auto sync bot

zhsj · zhsj · commit 9f6557532969 · 2019-04-04T10:24:32.000+08:00
diff --git a/faq/design.po b/faq/design.po
@@ -7,8 +7,9 @@
 # Yinuo Huang <yinuo.huang15@imperial.ac.uk>, 2018
 # ww song <sww4718168@gmail.com>, 2018
 # Freesand Leo <yuqinju@163.com>, 2019
-# tom smith, 2019
 # Shengjing Zhu <zsj950618@gmail.com>, 2019
+# Meng Du <alphanow@gmail.com>, 2019
+# tom smith, 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:42+0000\n"
-"Last-Translator: Shengjing Zhu <zsj950618@gmail.com>, 2019\n"
+"Last-Translator: tom smith, 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"
@@ -254,20 +255,20 @@ msgstr "许多习惯于C或Perl的人抱怨，他们想要使用C 的这个特
 
 #: ../../faq/design.rst:160
 msgid "where in Python you're forced to write this::"
-msgstr "但在Python中被强制写成这样："
+msgstr "但在Python中被强制写成这样::"
 
 #: ../../faq/design.rst:168
 msgid ""
 "The reason for not allowing assignment in Python expressions is a common, "
 "hard-to-find bug in those other languages, caused by this construct:"
-msgstr "不允许在python表达式中赋值的原因是这些其他语言中常见的、很难发现的错误，是由这个结构引起的："
+msgstr "不允许在 Python 表达式中赋值的原因是这些其他语言中常见的、很难发现的错误，是由这个结构引起的："
 
 #: ../../faq/design.rst:180
 msgid ""
 "The error is a simple typo: ``x = 0``, which assigns 0 to the variable "
 "``x``, was written while the comparison ``x == 0`` is certainly what was "
 "intended."
-msgstr "错误是一个简单的错字：``x = 0``，将0赋给变量``x``，而比较``x == 0``肯定是可以预期的。"
+msgstr "错误是一个简单的错字： ``x = 0`` ，将0赋给变量 ``x`` ，而比较 ``x == 0`` 肯定是可以预期的。"
 
 #: ../../faq/design.rst:183
 msgid ""
@@ -303,7 +304,7 @@ msgid ""
 " you have to remember to change two places in your program -- the second "
 "occurrence is hidden at the bottom of the loop."
 msgstr ""
-"问题在于，如果你改变主意（例如你想把它改成``sys.stdin.readline()``），如何知道下一行。你必须记住改变程序中的两个地方 -- "
+"问题在于，如果你改变主意（例如你想把它改成 ``sys.stdin.readline()`` ），如何知道下一行。你必须记住改变程序中的两个地方 -- "
 "第二次出现隐藏在循环的底部。"
 
 #: ../../faq/design.rst:206
@@ -333,8 +334,8 @@ msgid ""
 "problem. Compare the easy with which we rewrite a formula like x*(a+b) into "
 "x*a + x*b to the clumsiness of doing the same thing using a raw OO notation."
 msgstr ""
-"(a) 对于某些操作，前缀表示法比后缀更容易阅读 -- "
-"前缀（和中缀！）运算在数学中有着悠久的传统，就像在视觉上帮助数学家思考问题的记法。比较一下我们将x*（a+b）这样的公式改写为x*a+x*b的容易程度，以及使用原始OO符号做相同事情的笨拙程度。"
+"(a) 对于某些操作，前缀表示法比后缀更容易阅读 -- 前缀（和中缀！）运算在数学中有着悠久的传统，就像在视觉上帮助数学家思考问题的记法。比较一下我们将"
+" x*(a+b) 这样的公式改写为 x*a+x*b 的容易程度，以及使用原始OO符号做相同事情的笨拙程度。"
 
 #: ../../faq/design.rst:227
 msgid ""
@@ -405,7 +406,7 @@ msgstr ""
 msgid ""
 "is an instruction to a string literal to return the substrings delimited by "
 "the given separator (or, by default, arbitrary runs of white space)."
-msgstr "是对字符串文本的指令，用于返回由给定分隔符分隔的子字符串(或在默认情况下，返回任意空格)。"
+msgstr "是对字符串文本的指令，用于返回由给定分隔符分隔的子字符串（或在默认情况下，返回任意空格）。"
 
 #: ../../faq/design.rst:272
 msgid ""
@@ -420,27 +421,29 @@ msgstr ""
 
 #: ../../faq/design.rst:280
 msgid "How fast are exceptions?"
-msgstr ""
+msgstr "异常有多快？"
 
 #: ../../faq/design.rst:282
 msgid ""
 "A try/except block is extremely efficient if no exceptions are raised.  "
 "Actually catching an exception is expensive.  In versions of Python prior to"
 " 2.0 it was common to use this idiom::"
-msgstr ""
+msgstr "如果没有引发异常，则try/except块的效率极高。实际上捕获异常是昂贵的。在2.0之前的Python版本中，通常使用这个习惯用法::"
 
 #: ../../faq/design.rst:292
 msgid ""
 "This only made sense when you expected the dict to have the key almost all "
 "the time.  If that wasn't the case, you coded it like this::"
-msgstr ""
+msgstr "只有当你期望dict在任何时候都有key时，这才有意义。如果不是这样的话，你就是应该这样编码："
 
 #: ../../faq/design.rst:300
 msgid ""
 "For this specific case, you could also use ``value = dict.setdefault(key, "
 "getvalue(key))``, but only if the ``getvalue()`` call is cheap enough "
 "because it is evaluated in all cases."
 msgstr ""
+"对于这种特定的情况，您还可以使用 ``value = dict.setdefault(key, "
+"getvalue(key))``，但前提是调用``getvalue()`` 足够便宜，因为在所有情况下都会对其进行评估。"
 
 #: ../../faq/design.rst:306
 msgid "Why isn't there a switch or case statement in Python?"
@@ -453,33 +456,36 @@ msgid ""
 "there is no consensus (yet) on whether and how to do range tests.  See "
 ":pep:`275` for complete details and the current status."
 msgstr ""
+"你可以通过一系列 ``if... elif... elif... "
+"else``.轻松完成这项工作。对于switch语句语法已经有了一些建议，但尚未就是否以及如何进行范围测试达成共识。有关完整的详细信息和当前状态，请参阅"
+" :pep:`275` 。 "
 
 #: ../../faq/design.rst:313
 msgid ""
 "For cases where you need to choose from a very large number of "
 "possibilities, you can create a dictionary mapping case values to functions "
 "to call.  For example::"
-msgstr ""
+msgstr "对于需要从大量可能性中进行选择的情况，可以创建一个字典，将case 值映射到要调用的函数。例如："
 
 #: ../../faq/design.rst:327
 msgid ""
 "For calling methods on objects, you can simplify yet further by using the "
 ":func:`getattr` built-in to retrieve methods with a particular name::"
-msgstr ""
+msgstr "对于对象调用方法，可以通过使用 :func:`getattr` 内置检索具有特定名称的方法来进一步简化："
 
 #: ../../faq/design.rst:339
 msgid ""
 "It's suggested that you use a prefix for the method names, such as "
 "``visit_`` in this example.  Without such a prefix, if values are coming "
 "from an untrusted source, an attacker would be able to call any method on "
 "your object."
-msgstr ""
+msgstr "建议对方法名使用前缀，例如本例中的 ``visit_`` 。如果没有这样的前缀，如果值来自不受信任的源，攻击者将能够调用对象上的任何方法。"
 
 #: ../../faq/design.rst:345
 msgid ""
 "Can't you emulate threads in the interpreter instead of relying on an OS-"
 "specific thread implementation?"
-msgstr ""
+msgstr "难道不能在解释器中模拟线程，而非得依赖特定于操作系统的线程实现吗？"
 
 #: ../../faq/design.rst:347
 msgid ""
@@ -488,13 +494,16 @@ msgid ""
 "almost random moments.  Therefore, a complete threads implementation "
 "requires thread support for C."
 msgstr ""
+"答案1： 不幸的是，解释器为每个Python堆栈帧推送至少一个C堆栈帧。此外，扩展几乎随时回调Python。因此，一个完整的线程实现需要对C的线程支持。"
 
 #: ../../faq/design.rst:352
 msgid ""
 "Answer 2: Fortunately, there is `Stackless Python <https://github.com"
 "/stackless-dev/stackless/wiki>`_, which has a completely redesigned "
 "interpreter loop that avoids the C stack."
 msgstr ""
+"答案2： 幸运的是， `Stackless Python <https://github.com/stackless-"
+"dev/stackless/wiki>`_ 有一个完全重新设计的解释器循环，可以避免C堆栈。"
 
 #: ../../faq/design.rst:357
 msgid "Why can't lambda expressions contain statements?"
@@ -508,6 +517,9 @@ msgid ""
 "other languages, where they add functionality, Python lambdas are only a "
 "shorthand notation if you're too lazy to define a function."
 msgstr ""
+"Python的 "
+"lambda表达式不能包含语句，因为Python的语法框架不能处理嵌套在表达式内部的语句。然而，在Python中，这并不是一个严重的问题。与其他语言中添加功能的lambda表单不同，Python的"
+" lambdas只是一种速记符号，如果您懒得定义函数的话。"
 
 #: ../../faq/design.rst:365
 msgid ""
@@ -518,6 +530,8 @@ msgid ""
 "(which is exactly the same type of object that a lambda expression yields) "
 "is assigned!"
 msgstr ""
+"函数已经是Python中的第一类对象，可以在本地范围内声明。 因此，使用lambda而不是本地定义的函数的唯一优点是你不需要为函数创建一个名称 -- "
+"这只是一个分配了函数对象(与lambda表达式生成的对象类型完全相同)的局部变量！"
 
 #: ../../faq/design.rst:373
 msgid "Can Python be compiled to machine code, C or some other language?"
@@ -531,6 +545,9 @@ msgid ""
 "full Python language. For compiling to Java you can consider `VOC "
 "<https://voc.readthedocs.io>`_."
 msgstr ""
+"`Cython <http://cython.org/>`_ 将带有可选注释的Python修改版本编译到C扩展中。 `Nuitka "
+"<http://www.nuitka.net/>`_ 是一个将Python编译成 C++ "
+"代码的新兴编译器，旨在支持完整的Python语言。要编译成Java，可以考虑 `VOC <https://voc.readthedocs.io>`_ 。"
 
 #: ../../faq/design.rst:383
 msgid "How does Python manage memory?"
@@ -546,6 +563,9 @@ msgid ""
 "provides functions to perform a garbage collection, obtain debugging "
 "statistics, and tune the collector's parameters."
 msgstr ""
+"Python内存管理的细节取决于实现。Python的标准实现 "
+":term:`CPython`使用引用计数来检测不可访问的对象，并使用另一种机制来收集引用循环，定期执行循环检测算法来查找不可访问的循环并删除所涉及的对象。"
+" :mod:`gc` 模块提供了执行垃圾收集、获取调试统计信息和优化收集器参数的函数"
 
 #: ../../faq/design.rst:393
 msgid ""
@@ -555,12 +575,15 @@ msgid ""
 "porting problems if your Python code depends on the behavior of the "
 "reference counting implementation."
 msgstr ""
+"但是，其他实现(如  `Jython <http://www.jython.org>`_  或  `PyPy "
+"<http://www.pypy.org>`_ )，)可以依赖不同的机制，如完全的垃圾回收器 "
+"。如果你的Python代码依赖于引用计数实现的行为，则这种差异可能会导致一些微妙的移植问题。"
 
 #: ../../faq/design.rst:399
 msgid ""
 "In some Python implementations, the following code (which is fine in "
 "CPython) will probably run out of file descriptors::"
-msgstr ""
+msgstr "在一些Python实现中，以下代码（在CPython中工作的很好）可能会耗尽文件描述符::"
 
 #: ../../faq/design.rst:406
 msgid ""
@@ -569,13 +592,16 @@ msgid ""
 " those file objects will only get collected (and closed) at varying and "
 "possibly long intervals."
 msgstr ""
+"实际上，使用CPython的引用计数和析构函数方案， 每个新赋值的*f* "
+"都会关闭前一个文件。然而，对于传统的GC，这些文件对象只能以不同的时间间隔（可能很长的时间间隔）被收集（和关闭）。"
 
 #: ../../faq/design.rst:411
 msgid ""
 "If you want to write code that will work with any Python implementation, you"
 " should explicitly close the file or use the :keyword:`with` statement; this"
 " will work regardless of memory management scheme::"
 msgstr ""
+"如果要编写可用于任何python实现的代码，则应显式关闭该文件或使用  :keyword:`with` 语句；无论内存管理方案如何，这都有效："
 
 #: ../../faq/design.rst:421
 msgid "Why doesn't CPython use a more traditional garbage collection scheme?"
@@ -589,6 +615,8 @@ msgid ""
 "transparent, it isn't completely transparent; patches are required to get "
 "Python to work with it.)"
 msgstr ""
+"首先，这不是C标准特性，因此不能移植。(是的，我们知道Boehm "
+"GC库。它包含了*大多数*常见平台（但不是所有平台）的汇编代码，尽管它基本上是透明的，但也不是完全透明的; 要让Python使用它，需要使用补丁。)"
 
 #: ../../faq/design.rst:429
 msgid ""
@@ -599,6 +627,8 @@ msgid ""
 "malloc() and free(), and may not want Python's.  Right now, CPython works "
 "with anything that implements malloc() and free() properly."
 msgstr ""
+"当Python嵌入到其他应用程序中时，传统的GC也成为一个问题。在独立的Python中，可以用GC库提供的版本替换标准的malloc()和free()，嵌入Python的应用程序可能希望用"
+" *它自己* 替代malloc()和free()，而可能不需要Python的。现在，CPython可以正确地实现malloc()和free()。"
 
 #: ../../faq/design.rst:438
 msgid "Why isn't all memory freed when CPython exits?"
diff --git a/reference/import.po b/reference/import.po
@@ -1,21 +1,22 @@
 # SOME DESCRIPTIVE TITLE.
-# Copyright (C) 2001-2018, Python Software Foundation
+# Copyright (C) 2001-2019, Python Software Foundation
 # This file is distributed under the same license as the Python package.
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
 # 
 # Translators:
 # Jerry Chen <jerrychen9657@gmail.com>, 2017
 # eric R <trencyclopedia@gmail.com>, 2018
 # Freesand Leo <yuqinju@163.com>, 2018
+# Meng Du <alphanow@gmail.com>, 2019
 # 
 #, fuzzy
 msgid ""
 msgstr ""
 "Project-Id-Version: Python 3.7\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-12-20 10:06+0900\n"
+"POT-Creation-Date: 2019-01-01 10:14+0900\n"
 "PO-Revision-Date: 2017-02-16 23:38+0000\n"
-"Last-Translator: Freesand Leo <yuqinju@163.com>, 2018\n"
+"Last-Translator: Meng Du <alphanow@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"
@@ -317,9 +318,9 @@ msgid ""
 " to ``None``, forcing the next import of the module to result in a "
 ":exc:`ModuleNotFoundError`."
 msgstr ""
-":data:`sys.modules` 是可写的。 删除一个键不会销毁关联的模块（因为其他模块可能还在引用它），但会使得该名称的模块在缓存中不可用，导致"
-" Python 在下次导入时需要重新搜索该名称的模块。 键也可以被同仁为 ``None``，这将导致下次导入该模块时引发 "
-":exc:`ModuleNotFoundError`。"
+":data:`sys.modules` 是可写的。删除键可能不会破坏关联的模块（因为其他模块可能会保留对它的引用），但它会使命名模块的缓存条目无效，导致"
+" Python 在下次导入时重新搜索命名模块。键也可以分配给 ``None`` ，强制下一次导入模块导致 "
+":exc:`ModuleNotFoundError` 。"
 
 #: ../../reference/import.rst:198
 msgid ""
diff --git a/whatsnew/changelog.po b/whatsnew/changelog.po
