@@ -617,32 +617,35 @@ msgid ""
617617"should be executed. In its simplest form (that can't already be handled just"
618618" by using an ``except`` clause instead), it looks something like this::"
619619msgstr ""
620+ "一种你有时将看到的模式是 ``try-finally`` 语句附带一个变量来指明 ``finally`` 子句体是否要被执行。 "
621+ "在其最简单的形式中(它无法仅仅通过改用一条 ``except`` 子句来预先处理),看起来会是这样::"
620622
621623#: ../../library/contextlib.rst:617
622624msgid ""
623625"As with any ``try`` statement based code, this can cause problems for "
624626"development and review, because the setup code and the cleanup code can end "
625627"up being separated by arbitrarily long sections of code."
626- msgstr ""
628+ msgstr "就如任何基于 ``try`` 语句的代码一样,这可能会导致开发和审查方面的问题,因为设置代码和清理代码最终可能会被任意长的代码部分所分隔。 "
627629
628630#: ../../library/contextlib.rst:621
629631msgid ""
630632":class:`ExitStack` makes it possible to instead register a callback for "
631633"execution at the end of a ``with`` statement, and then later decide to skip "
632634"executing that callback::"
633635msgstr ""
636+ ":class:`ExitStack` 将允许选择在一条 ``with`` 语句末尾注册一个用于执行的回调的替代方式,等以后再决定是否跳过该回调的执行::"
634637
635638#: ../../library/contextlib.rst:633
636639msgid ""
637640"This allows the intended cleanup up behaviour to be made explicit up front, "
638641"rather than requiring a separate flag variable."
639- msgstr ""
642+ msgstr "这允许在事先显式地指明预期的清理行为,而不需要一个单独的旗标变量。 "
640643
641644#: ../../library/contextlib.rst:636
642645msgid ""
643646"If a particular application uses this pattern a lot, it can be simplified "
644647"even further by means of a small helper class::"
645- msgstr ""
648+ msgstr "如果某个应用程序大量使用此模式,则可以通过使用一个较小的辅助类来进一步地简化它:: "
646649
647650#: ../../library/contextlib.rst:654
648651msgid ""
0 commit comments