|
7 | 7 | msgstr ""
|
8 | 8 | "Project-Id-Version: Python 3.11\n"
|
9 | 9 | "Report-Msgid-Bugs-To: \n"
|
10 |
| -"POT-Creation-Date: 2022-07-06 00:17+0000\n" |
| 10 | +"POT-Creation-Date: 2023-01-21 00:16+0000\n" |
11 | 11 | "PO-Revision-Date: 2018-05-23 16:07+0000\n"
|
12 | 12 | "Last-Translator: Adrian Liaw <adrianliaw2000@gmail.com>\n"
|
13 | 13 | "Language-Team: Chinese - TAIWAN (https://github.com/python/python-docs-zh-"
|
@@ -152,8 +152,8 @@ msgstr ""
|
152 | 152 |
|
153 | 153 | #: ../../library/optparse.rst:125
|
154 | 154 | msgid ""
|
155 |
| -"a plus sign followed by a single letter, or a few letters, or a word, e.g. ``" |
156 |
| -"+f``, ``+rgb``" |
| 155 | +"a plus sign followed by a single letter, or a few letters, or a word, e.g. " |
| 156 | +"``+f``, ``+rgb``" |
157 | 157 | msgstr ""
|
158 | 158 |
|
159 | 159 | #: ../../library/optparse.rst:128
|
@@ -527,7 +527,7 @@ msgid "``\"store_const\"``"
|
527 | 527 | msgstr "``\"store_const\"``"
|
528 | 528 |
|
529 | 529 | #: ../../library/optparse.rst:407 ../../library/optparse.rst:928
|
530 |
| -msgid "store a constant value" |
| 530 | +msgid "store a constant value, pre-set via :attr:`Option.const`" |
531 | 531 | msgstr ""
|
532 | 532 |
|
533 | 533 | #: ../../library/optparse.rst:410 ../../library/optparse.rst:937
|
@@ -566,10 +566,10 @@ msgstr ""
|
566 | 566 |
|
567 | 567 | #: ../../library/optparse.rst:427
|
568 | 568 | msgid ""
|
569 |
| -"All of the above examples involve setting some variable (the \"destination" |
570 |
| -"\") when certain command-line options are seen. What happens if those " |
571 |
| -"options are never seen? Since we didn't supply any defaults, they are all " |
572 |
| -"set to ``None``. This is usually fine, but sometimes you want more " |
| 569 | +"All of the above examples involve setting some variable (the " |
| 570 | +"\"destination\") when certain command-line options are seen. What happens " |
| 571 | +"if those options are never seen? Since we didn't supply any defaults, they " |
| 572 | +"are all set to ``None``. This is usually fine, but sometimes you want more " |
573 | 573 | "control. :mod:`optparse` lets you supply a default value for each "
|
574 | 574 | "destination, which is assigned before the command line is parsed."
|
575 | 575 | msgstr ""
|
@@ -813,8 +813,8 @@ msgstr ""
|
813 | 813 | #: ../../library/optparse.rst:692
|
814 | 814 | msgid ""
|
815 | 815 | "Print the version message for the current program (``self.version``) to "
|
816 |
| -"*file* (default stdout). As with :meth:`print_usage`, any occurrence of ``" |
817 |
| -"%prog`` in ``self.version`` is replaced with the name of the current " |
| 816 | +"*file* (default stdout). As with :meth:`print_usage`, any occurrence of " |
| 817 | +"``%prog`` in ``self.version`` is replaced with the name of the current " |
818 | 818 | "program. Does nothing if ``self.version`` is empty or undefined."
|
819 | 819 | msgstr ""
|
820 | 820 |
|
@@ -916,8 +916,8 @@ msgstr ""
|
916 | 916 | #: ../../library/optparse.rst:810
|
917 | 917 | msgid ""
|
918 | 918 | "The usage summary to print when your program is run incorrectly or with a "
|
919 |
| -"help option. When :mod:`optparse` prints the usage string, it expands ``" |
920 |
| -"%prog`` to ``os.path.basename(sys.argv[0])`` (or to ``prog`` if you passed " |
| 919 | +"help option. When :mod:`optparse` prints the usage string, it expands " |
| 920 | +"``%prog`` to ``os.path.basename(sys.argv[0])`` (or to ``prog`` if you passed " |
921 | 921 | "that keyword argument). To suppress a usage message, pass the special "
|
922 | 922 | "value :data:`optparse.SUPPRESS_USAGE`."
|
923 | 923 | msgstr ""
|
@@ -951,8 +951,8 @@ msgstr ""
|
951 | 951 | msgid ""
|
952 | 952 | "A version string to print when the user supplies a version option. If you "
|
953 | 953 | "supply a true value for ``version``, :mod:`optparse` automatically adds a "
|
954 |
| -"version option with the single option string ``--version``. The substring ``" |
955 |
| -"%prog`` is expanded the same as for ``usage``." |
| 954 | +"version option with the single option string ``--version``. The substring " |
| 955 | +"``%prog`` is expanded the same as for ``usage``." |
956 | 956 | msgstr ""
|
957 | 957 |
|
958 | 958 | #: ../../library/optparse.rst:835
|
@@ -1123,7 +1123,7 @@ msgid "``\"append_const\"``"
|
1123 | 1123 | msgstr "``\"append_const\"``"
|
1124 | 1124 |
|
1125 | 1125 | #: ../../library/optparse.rst:940
|
1126 |
| -msgid "append a constant value to a list" |
| 1126 | +msgid "append a constant value to a list, pre-set via :attr:`Option.const`" |
1127 | 1127 | msgstr ""
|
1128 | 1128 |
|
1129 | 1129 | #: ../../library/optparse.rst:949 ../../library/optparse.rst:1226
|
@@ -1214,8 +1214,8 @@ msgstr ""
|
1214 | 1214 |
|
1215 | 1215 | #: ../../library/optparse.rst:1011
|
1216 | 1216 | msgid ""
|
1217 |
| -"The argument type expected by this option (e.g., ``\"string\"`` or ``\"int" |
1218 |
| -"\"``); the available option types are documented :ref:`here <optparse-" |
| 1217 | +"The argument type expected by this option (e.g., ``\"string\"`` or " |
| 1218 | +"``\"int\"``); the available option types are documented :ref:`here <optparse-" |
1219 | 1219 | "standard-option-types>`."
|
1220 | 1220 | msgstr ""
|
1221 | 1221 |
|
@@ -1770,11 +1770,11 @@ msgstr ""
|
1770 | 1770 | #: ../../library/optparse.rst:1452
|
1771 | 1771 | msgid ""
|
1772 | 1772 | "At this point, :mod:`optparse` detects that a previously added option is "
|
1773 |
| -"already using the ``-n`` option string. Since ``conflict_handler`` is ``" |
1774 |
| -"\"resolve\"``, it resolves the situation by removing ``-n`` from the earlier " |
1775 |
| -"option's list of option strings. Now ``--dry-run`` is the only way for the " |
1776 |
| -"user to activate that option. If the user asks for help, the help message " |
1777 |
| -"will reflect that::" |
| 1773 | +"already using the ``-n`` option string. Since ``conflict_handler`` is " |
| 1774 | +"``\"resolve\"``, it resolves the situation by removing ``-n`` from the " |
| 1775 | +"earlier option's list of option strings. Now ``--dry-run`` is the only way " |
| 1776 | +"for the user to activate that option. If the user asks for help, the help " |
| 1777 | +"message will reflect that::" |
1778 | 1778 | msgstr ""
|
1779 | 1779 |
|
1780 | 1780 | #: ../../library/optparse.rst:1463
|
@@ -1982,8 +1982,8 @@ msgid ""
|
1982 | 1982 | "is the option string seen on the command-line that's triggering the "
|
1983 | 1983 | "callback. (If an abbreviated long option was used, ``opt_str`` will be the "
|
1984 | 1984 | "full, canonical option string---e.g. if the user puts ``--foo`` on the "
|
1985 |
| -"command-line as an abbreviation for ``--foobar``, then ``opt_str`` will be ``" |
1986 |
| -"\"--foobar\"``.)" |
| 1985 | +"command-line as an abbreviation for ``--foobar``, then ``opt_str`` will be " |
| 1986 | +"``\"--foobar\"``.)" |
1987 | 1987 | msgstr ""
|
1988 | 1988 |
|
1989 | 1989 | #: ../../library/optparse.rst:1637
|
@@ -2333,10 +2333,10 @@ msgstr ""
|
2333 | 2333 |
|
2334 | 2334 | #: ../../library/optparse.rst:1950
|
2335 | 2335 | msgid ""
|
2336 |
| -"These are overlapping sets: some default \"store\" actions are ``\"store" |
2337 |
| -"\"``, ``\"store_const\"``, ``\"append\"``, and ``\"count\"``, while the " |
2338 |
| -"default \"typed\" actions are ``\"store\"``, ``\"append\"``, and ``\"callback" |
2339 |
| -"\"``." |
| 2336 | +"These are overlapping sets: some default \"store\" actions are " |
| 2337 | +"``\"store\"``, ``\"store_const\"``, ``\"append\"``, and ``\"count\"``, while " |
| 2338 | +"the default \"typed\" actions are ``\"store\"``, ``\"append\"``, and " |
| 2339 | +"``\"callback\"``." |
2340 | 2340 | msgstr ""
|
2341 | 2341 |
|
2342 | 2342 | #: ../../library/optparse.rst:1954
|
@@ -2425,11 +2425,11 @@ msgstr ""
|
2425 | 2425 | msgid ""
|
2426 | 2426 | "If the ``attr`` attribute of ``values`` doesn't exist or is ``None``, then "
|
2427 | 2427 | "ensure_value() first sets it to ``value``, and then returns 'value. This is "
|
2428 |
| -"very handy for actions like ``\"extend\"``, ``\"append\"``, and ``\"count" |
2429 |
| -"\"``, all of which accumulate data in a variable and expect that variable to " |
2430 |
| -"be of a certain type (a list for the first two, an integer for the latter). " |
2431 |
| -"Using :meth:`ensure_value` means that scripts using your action don't have " |
2432 |
| -"to worry about setting a default value for the option destinations in " |
2433 |
| -"question; they can just leave the default as ``None`` and :meth:" |
2434 |
| -"`ensure_value` will take care of getting it right when it's needed." |
| 2428 | +"very handy for actions like ``\"extend\"``, ``\"append\"``, and " |
| 2429 | +"``\"count\"``, all of which accumulate data in a variable and expect that " |
| 2430 | +"variable to be of a certain type (a list for the first two, an integer for " |
| 2431 | +"the latter). Using :meth:`ensure_value` means that scripts using your " |
| 2432 | +"action don't have to worry about setting a default value for the option " |
| 2433 | +"destinations in question; they can just leave the default as ``None`` and :" |
| 2434 | +"meth:`ensure_value` will take care of getting it right when it's needed." |
2435 | 2435 | msgstr ""
|
0 commit comments