forked from python/python-docs-tr
-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathargparse.po
More file actions
2021 lines (1694 loc) · 64 KB
/
argparse.po
File metadata and controls
2021 lines (1694 loc) · 64 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
# Python Documentation Turkish Translation
# Copyright (C) 2001-2022, Python Software Foundation
# This file is distributed under the same license as the Python package.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.11\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-12-17 01:28+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: \n"
"Language-Team: TURKISH <python.docs.tr@gmail.com>\n"
"Language: tr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: library/argparse.rst:2
msgid ""
":mod:`argparse` --- Parser for command-line options, arguments and sub-"
"commands"
msgstr ""
#: library/argparse.rst:12
msgid "**Source code:** :source:`Lib/argparse.py`"
msgstr ""
#: library/argparse.rst:None
msgid "Tutorial"
msgstr ""
#: library/argparse.rst:18
msgid ""
"This page contains the API reference information. For a more gentle "
"introduction to Python command-line parsing, have a look at the :ref:"
"`argparse tutorial <argparse-tutorial>`."
msgstr ""
#: library/argparse.rst:22
msgid ""
"The :mod:`argparse` module makes it easy to write user-friendly command-line "
"interfaces. The program defines what arguments it requires, and :mod:"
"`argparse` will figure out how to parse those out of :data:`sys.argv`. The :"
"mod:`argparse` module also automatically generates help and usage messages. "
"The module will also issue errors when users give the program invalid "
"arguments."
msgstr ""
#: library/argparse.rst:30
msgid "Core Functionality"
msgstr ""
#: library/argparse.rst:32
msgid ""
"The :mod:`argparse` module's support for command-line interfaces is built "
"around an instance of :class:`argparse.ArgumentParser`. It is a container "
"for argument specifications and has options that apply the parser as whole::"
msgstr ""
#: library/argparse.rst:41
msgid ""
"The :meth:`ArgumentParser.add_argument` method attaches individual argument "
"specifications to the parser. It supports positional arguments, options "
"that accept values, and on/off flags::"
msgstr ""
#: library/argparse.rst:50
msgid ""
"The :meth:`ArgumentParser.parse_args` method runs the parser and places the "
"extracted data in a :class:`argparse.Namespace` object::"
msgstr ""
#: library/argparse.rst:58
msgid "Quick Links for add_argument()"
msgstr ""
#: library/argparse.rst:61
msgid "Name"
msgstr ""
#: library/argparse.rst:61
msgid "Description"
msgstr ""
#: library/argparse.rst:61
msgid "Values"
msgstr ""
#: library/argparse.rst:63
msgid "action_"
msgstr ""
#: library/argparse.rst:63
msgid "Specify how an argument should be handled"
msgstr ""
#: library/argparse.rst:63
msgid ""
"``'store'``, ``'store_const'``, ``'store_true'``, ``'append'``, "
"``'append_const'``, ``'count'``, ``'help'``, ``'version'``"
msgstr ""
#: library/argparse.rst:64
msgid "choices_"
msgstr ""
#: library/argparse.rst:64
msgid "Limit values to a specific set of choices"
msgstr ""
#: library/argparse.rst:64
msgid ""
"``['foo', 'bar']``, ``range(1, 10)``, or :class:`~collections.abc.Container` "
"instance"
msgstr ""
#: library/argparse.rst:65
msgid "const_"
msgstr ""
#: library/argparse.rst:65
msgid "Store a constant value"
msgstr ""
#: library/argparse.rst:66
msgid "default_"
msgstr ""
#: library/argparse.rst:66
msgid "Default value used when an argument is not provided"
msgstr ""
#: library/argparse.rst:66
msgid "Defaults to ``None``"
msgstr ""
#: library/argparse.rst:67
msgid "dest_"
msgstr ""
#: library/argparse.rst:67
msgid "Specify the attribute name used in the result namespace"
msgstr ""
#: library/argparse.rst:68
msgid "help_"
msgstr ""
#: library/argparse.rst:68
msgid "Help message for an argument"
msgstr ""
#: library/argparse.rst:69
msgid "metavar_"
msgstr ""
#: library/argparse.rst:69
msgid "Alternate display name for the argument as shown in help"
msgstr ""
#: library/argparse.rst:70
msgid "nargs_"
msgstr ""
#: library/argparse.rst:70
msgid "Number of times the argument can be used"
msgstr ""
#: library/argparse.rst:70
msgid ":class:`int`, ``'?'``, ``'*'``, ``'+'``, or ``argparse.REMAINDER``"
msgstr ""
#: library/argparse.rst:71
msgid "required_"
msgstr ""
#: library/argparse.rst:71
msgid "Indicate whether an argument is required or optional"
msgstr ""
#: library/argparse.rst:71
msgid "``True`` or ``False``"
msgstr ""
#: library/argparse.rst:72
msgid "type_"
msgstr ""
#: library/argparse.rst:72
msgid "Automatically convert an argument to the given type"
msgstr ""
#: library/argparse.rst:72
msgid ""
":class:`int`, :class:`float`, ``argparse.FileType('w')``, or callable "
"function"
msgstr ""
#: library/argparse.rst:77
msgid "Example"
msgstr ""
#: library/argparse.rst:79
msgid ""
"The following code is a Python program that takes a list of integers and "
"produces either the sum or the max::"
msgstr ""
#: library/argparse.rst:94
msgid ""
"Assuming the above Python code is saved into a file called ``prog.py``, it "
"can be run at the command line and it provides useful help messages:"
msgstr ""
#: library/argparse.rst:111
msgid ""
"When run with the appropriate arguments, it prints either the sum or the max "
"of the command-line integers:"
msgstr ""
#: library/argparse.rst:122
msgid "If invalid arguments are passed in, an error will be displayed:"
msgstr ""
#: library/argparse.rst:130
msgid "The following sections walk you through this example."
msgstr ""
#: library/argparse.rst:134
msgid "Creating a parser"
msgstr ""
#: library/argparse.rst:136
msgid ""
"The first step in using the :mod:`argparse` is creating an :class:"
"`ArgumentParser` object::"
msgstr ""
#: library/argparse.rst:141
msgid ""
"The :class:`ArgumentParser` object will hold all the information necessary "
"to parse the command line into Python data types."
msgstr ""
#: library/argparse.rst:146
msgid "Adding arguments"
msgstr ""
#: library/argparse.rst:148
msgid ""
"Filling an :class:`ArgumentParser` with information about program arguments "
"is done by making calls to the :meth:`~ArgumentParser.add_argument` method. "
"Generally, these calls tell the :class:`ArgumentParser` how to take the "
"strings on the command line and turn them into objects. This information is "
"stored and used when :meth:`~ArgumentParser.parse_args` is called. For "
"example::"
msgstr ""
#: library/argparse.rst:160
msgid ""
"Later, calling :meth:`~ArgumentParser.parse_args` will return an object with "
"two attributes, ``integers`` and ``accumulate``. The ``integers`` attribute "
"will be a list of one or more integers, and the ``accumulate`` attribute "
"will be either the :func:`sum` function, if ``--sum`` was specified at the "
"command line, or the :func:`max` function if it was not."
msgstr ""
#: library/argparse.rst:168
msgid "Parsing arguments"
msgstr ""
#: library/argparse.rst:170
msgid ""
":class:`ArgumentParser` parses arguments through the :meth:`~ArgumentParser."
"parse_args` method. This will inspect the command line, convert each "
"argument to the appropriate type and then invoke the appropriate action. In "
"most cases, this means a simple :class:`Namespace` object will be built up "
"from attributes parsed out of the command line::"
msgstr ""
#: library/argparse.rst:179
msgid ""
"In a script, :meth:`~ArgumentParser.parse_args` will typically be called "
"with no arguments, and the :class:`ArgumentParser` will automatically "
"determine the command-line arguments from :data:`sys.argv`."
msgstr ""
#: library/argparse.rst:185
msgid "ArgumentParser objects"
msgstr ""
#: library/argparse.rst:194
msgid ""
"Create a new :class:`ArgumentParser` object. All parameters should be passed "
"as keyword arguments. Each parameter has its own more detailed description "
"below, but in short they are:"
msgstr ""
#: library/argparse.rst:198
msgid ""
"prog_ - The name of the program (default: ``os.path.basename(sys.argv[0])``)"
msgstr ""
#: library/argparse.rst:201
msgid ""
"usage_ - The string describing the program usage (default: generated from "
"arguments added to parser)"
msgstr ""
#: library/argparse.rst:204
msgid ""
"description_ - Text to display before the argument help (by default, no text)"
msgstr ""
#: library/argparse.rst:207
msgid "epilog_ - Text to display after the argument help (by default, no text)"
msgstr ""
#: library/argparse.rst:209
msgid ""
"parents_ - A list of :class:`ArgumentParser` objects whose arguments should "
"also be included"
msgstr ""
#: library/argparse.rst:212
msgid "formatter_class_ - A class for customizing the help output"
msgstr ""
#: library/argparse.rst:214
msgid ""
"prefix_chars_ - The set of characters that prefix optional arguments "
"(default: '-')"
msgstr ""
#: library/argparse.rst:217
msgid ""
"fromfile_prefix_chars_ - The set of characters that prefix files from which "
"additional arguments should be read (default: ``None``)"
msgstr ""
#: library/argparse.rst:220
msgid ""
"argument_default_ - The global default value for arguments (default: "
"``None``)"
msgstr ""
#: library/argparse.rst:223
msgid ""
"conflict_handler_ - The strategy for resolving conflicting optionals "
"(usually unnecessary)"
msgstr ""
#: library/argparse.rst:226
msgid ""
"add_help_ - Add a ``-h/--help`` option to the parser (default: ``True``)"
msgstr ""
#: library/argparse.rst:228
msgid ""
"allow_abbrev_ - Allows long options to be abbreviated if the abbreviation is "
"unambiguous. (default: ``True``)"
msgstr ""
#: library/argparse.rst:231
msgid ""
"exit_on_error_ - Determines whether or not ArgumentParser exits with error "
"info when an error occurs. (default: ``True``)"
msgstr ""
#: library/argparse.rst:234
msgid "*allow_abbrev* parameter was added."
msgstr ""
#: library/argparse.rst:237
msgid ""
"In previous versions, *allow_abbrev* also disabled grouping of short flags "
"such as ``-vv`` to mean ``-v -v``."
msgstr ""
#: library/argparse.rst:241
msgid "*exit_on_error* parameter was added."
msgstr ""
#: library/argparse.rst:770
msgid "The following sections describe how each of these are used."
msgstr ""
#: library/argparse.rst:250
msgid "prog"
msgstr ""
#: library/argparse.rst:252
msgid ""
"By default, :class:`ArgumentParser` objects use ``sys.argv[0]`` to determine "
"how to display the name of the program in help messages. This default is "
"almost always desirable because it will make the help messages match how the "
"program was invoked on the command line. For example, consider a file named "
"``myprogram.py`` with the following code::"
msgstr ""
#: library/argparse.rst:263
msgid ""
"The help for this program will display ``myprogram.py`` as the program name "
"(regardless of where the program was invoked from):"
msgstr ""
#: library/argparse.rst:282
msgid ""
"To change this default behavior, another value can be supplied using the "
"``prog=`` argument to :class:`ArgumentParser`::"
msgstr ""
#: library/argparse.rst:292
msgid ""
"Note that the program name, whether determined from ``sys.argv[0]`` or from "
"the ``prog=`` argument, is available to help messages using the ``%(prog)s`` "
"format specifier."
msgstr ""
#: library/argparse.rst:309
msgid "usage"
msgstr ""
#: library/argparse.rst:311
msgid ""
"By default, :class:`ArgumentParser` calculates the usage message from the "
"arguments it contains::"
msgstr ""
#: library/argparse.rst:327
msgid ""
"The default message can be overridden with the ``usage=`` keyword argument::"
msgstr ""
#: library/argparse.rst:342
msgid ""
"The ``%(prog)s`` format specifier is available to fill in the program name "
"in your usage messages."
msgstr ""
#: library/argparse.rst:349
msgid "description"
msgstr ""
#: library/argparse.rst:351
msgid ""
"Most calls to the :class:`ArgumentParser` constructor will use the "
"``description=`` keyword argument. This argument gives a brief description "
"of what the program does and how it works. In help messages, the "
"description is displayed between the command-line usage string and the help "
"messages for the various arguments::"
msgstr ""
#: library/argparse.rst:366
msgid ""
"By default, the description will be line-wrapped so that it fits within the "
"given space. To change this behavior, see the formatter_class_ argument."
msgstr ""
#: library/argparse.rst:371
msgid "epilog"
msgstr ""
#: library/argparse.rst:373
msgid ""
"Some programs like to display additional description of the program after "
"the description of the arguments. Such text can be specified using the "
"``epilog=`` argument to :class:`ArgumentParser`::"
msgstr ""
#: library/argparse.rst:390
msgid ""
"As with the description_ argument, the ``epilog=`` text is by default line-"
"wrapped, but this behavior can be adjusted with the formatter_class_ "
"argument to :class:`ArgumentParser`."
msgstr ""
#: library/argparse.rst:396
msgid "parents"
msgstr ""
#: library/argparse.rst:398
msgid ""
"Sometimes, several parsers share a common set of arguments. Rather than "
"repeating the definitions of these arguments, a single parser with all the "
"shared arguments and passed to ``parents=`` argument to :class:"
"`ArgumentParser` can be used. The ``parents=`` argument takes a list of :"
"class:`ArgumentParser` objects, collects all the positional and optional "
"actions from them, and adds these actions to the :class:`ArgumentParser` "
"object being constructed::"
msgstr ""
#: library/argparse.rst:418
msgid ""
"Note that most parent parsers will specify ``add_help=False``. Otherwise, "
"the :class:`ArgumentParser` will see two ``-h/--help`` options (one in the "
"parent and one in the child) and raise an error."
msgstr ""
#: library/argparse.rst:423
msgid ""
"You must fully initialize the parsers before passing them via ``parents=``. "
"If you change the parent parsers after the child parser, those changes will "
"not be reflected in the child."
msgstr ""
#: library/argparse.rst:431
msgid "formatter_class"
msgstr ""
#: library/argparse.rst:433
msgid ""
":class:`ArgumentParser` objects allow the help formatting to be customized "
"by specifying an alternate formatting class. Currently, there are four such "
"classes:"
msgstr ""
#: library/argparse.rst:442
msgid ""
":class:`RawDescriptionHelpFormatter` and :class:`RawTextHelpFormatter` give "
"more control over how textual descriptions are displayed. By default, :class:"
"`ArgumentParser` objects line-wrap the description_ and epilog_ texts in "
"command-line help messages::"
msgstr ""
#: library/argparse.rst:467
msgid ""
"Passing :class:`RawDescriptionHelpFormatter` as ``formatter_class=`` "
"indicates that description_ and epilog_ are already correctly formatted and "
"should not be line-wrapped::"
msgstr ""
#: library/argparse.rst:493
msgid ""
":class:`RawTextHelpFormatter` maintains whitespace for all sorts of help "
"text, including argument descriptions. However, multiple new lines are "
"replaced with one. If you wish to preserve multiple blank lines, add spaces "
"between the newlines."
msgstr ""
#: library/argparse.rst:498
msgid ""
":class:`ArgumentDefaultsHelpFormatter` automatically adds information about "
"default values to each of the argument help messages::"
msgstr ""
#: library/argparse.rst:516
msgid ""
":class:`MetavarTypeHelpFormatter` uses the name of the type_ argument for "
"each argument as the display name for its values (rather than using the "
"dest_ as the regular formatter does)::"
msgstr ""
#: library/argparse.rst:537
msgid "prefix_chars"
msgstr ""
#: library/argparse.rst:539
msgid ""
"Most command-line options will use ``-`` as the prefix, e.g. ``-f/--foo``. "
"Parsers that need to support different or additional prefix characters, e.g. "
"for options like ``+f`` or ``/foo``, may specify them using the "
"``prefix_chars=`` argument to the ArgumentParser constructor::"
msgstr ""
#: library/argparse.rst:551
msgid ""
"The ``prefix_chars=`` argument defaults to ``'-'``. Supplying a set of "
"characters that does not include ``-`` will cause ``-f/--foo`` options to be "
"disallowed."
msgstr ""
#: library/argparse.rst:557
msgid "fromfile_prefix_chars"
msgstr ""
#: library/argparse.rst:559
msgid ""
"Sometimes, when dealing with a particularly long argument list, it may make "
"sense to keep the list of arguments in a file rather than typing it out at "
"the command line. If the ``fromfile_prefix_chars=`` argument is given to "
"the :class:`ArgumentParser` constructor, then arguments that start with any "
"of the specified characters will be treated as files, and will be replaced "
"by the arguments they contain. For example::"
msgstr ""
#: library/argparse.rst:573
msgid ""
"Arguments read from a file must by default be one per line (but see also :"
"meth:`~ArgumentParser.convert_arg_line_to_args`) and are treated as if they "
"were in the same place as the original file referencing argument on the "
"command line. So in the example above, the expression ``['-f', 'foo', "
"'@args.txt']`` is considered equivalent to the expression ``['-f', 'foo', '-"
"f', 'bar']``."
msgstr ""
#: library/argparse.rst:579
msgid ""
"The ``fromfile_prefix_chars=`` argument defaults to ``None``, meaning that "
"arguments will never be treated as file references."
msgstr ""
#: library/argparse.rst:584
msgid "argument_default"
msgstr ""
#: library/argparse.rst:586
msgid ""
"Generally, argument defaults are specified either by passing a default to :"
"meth:`~ArgumentParser.add_argument` or by calling the :meth:`~ArgumentParser."
"set_defaults` methods with a specific set of name-value pairs. Sometimes "
"however, it may be useful to specify a single parser-wide default for "
"arguments. This can be accomplished by passing the ``argument_default=`` "
"keyword argument to :class:`ArgumentParser`. For example, to globally "
"suppress attribute creation on :meth:`~ArgumentParser.parse_args` calls, we "
"supply ``argument_default=SUPPRESS``::"
msgstr ""
#: library/argparse.rst:606
msgid "allow_abbrev"
msgstr ""
#: library/argparse.rst:608
msgid ""
"Normally, when you pass an argument list to the :meth:`~ArgumentParser."
"parse_args` method of an :class:`ArgumentParser`, it :ref:`recognizes "
"abbreviations <prefix-matching>` of long options."
msgstr ""
#: library/argparse.rst:612
msgid "This feature can be disabled by setting ``allow_abbrev`` to ``False``::"
msgstr ""
#: library/argparse.rst:625
msgid "conflict_handler"
msgstr ""
#: library/argparse.rst:627
msgid ""
":class:`ArgumentParser` objects do not allow two actions with the same "
"option string. By default, :class:`ArgumentParser` objects raise an "
"exception if an attempt is made to create an argument with an option string "
"that is already in use::"
msgstr ""
#: library/argparse.rst:639
msgid ""
"Sometimes (e.g. when using parents_) it may be useful to simply override any "
"older arguments with the same option string. To get this behavior, the "
"value ``'resolve'`` can be supplied to the ``conflict_handler=`` argument "
"of :class:`ArgumentParser`::"
msgstr ""
#: library/argparse.rst:655
msgid ""
"Note that :class:`ArgumentParser` objects only remove an action if all of "
"its option strings are overridden. So, in the example above, the old ``-f/--"
"foo`` action is retained as the ``-f`` action, because only the ``--foo`` "
"option string was overridden."
msgstr ""
#: library/argparse.rst:662
msgid "add_help"
msgstr ""
#: library/argparse.rst:664
msgid ""
"By default, ArgumentParser objects add an option which simply displays the "
"parser's help message. For example, consider a file named ``myprogram.py`` "
"containing the following code::"
msgstr ""
#: library/argparse.rst:673
msgid ""
"If ``-h`` or ``--help`` is supplied at the command line, the ArgumentParser "
"help will be printed:"
msgstr ""
#: library/argparse.rst:685
msgid ""
"Occasionally, it may be useful to disable the addition of this help option. "
"This can be achieved by passing ``False`` as the ``add_help=`` argument to :"
"class:`ArgumentParser`::"
msgstr ""
#: library/argparse.rst:697
msgid ""
"The help option is typically ``-h/--help``. The exception to this is if the "
"``prefix_chars=`` is specified and does not include ``-``, in which case ``-"
"h`` and ``--help`` are not valid options. In this case, the first character "
"in ``prefix_chars`` is used to prefix the help options::"
msgstr ""
#: library/argparse.rst:712
msgid "exit_on_error"
msgstr ""
#: library/argparse.rst:714
msgid ""
"Normally, when you pass an invalid argument list to the :meth:"
"`~ArgumentParser.parse_args` method of an :class:`ArgumentParser`, it will "
"exit with error info."
msgstr ""
#: library/argparse.rst:717
msgid ""
"If the user would like to catch errors manually, the feature can be enabled "
"by setting ``exit_on_error`` to ``False``::"
msgstr ""
#: library/argparse.rst:734
msgid "The add_argument() method"
msgstr ""
#: library/argparse.rst:740
msgid ""
"Define how a single command-line argument should be parsed. Each parameter "
"has its own more detailed description below, but in short they are:"
msgstr ""
#: library/argparse.rst:743
msgid ""
"`name or flags`_ - Either a name or a list of option strings, e.g. ``foo`` "
"or ``-f, --foo``."
msgstr ""
#: library/argparse.rst:746
msgid ""
"action_ - The basic type of action to be taken when this argument is "
"encountered at the command line."
msgstr ""
#: library/argparse.rst:749
msgid "nargs_ - The number of command-line arguments that should be consumed."
msgstr ""
#: library/argparse.rst:751
msgid ""
"const_ - A constant value required by some action_ and nargs_ selections."
msgstr ""
#: library/argparse.rst:753
msgid ""
"default_ - The value produced if the argument is absent from the command "
"line and if it is absent from the namespace object."
msgstr ""
#: library/argparse.rst:756
msgid ""
"type_ - The type to which the command-line argument should be converted."
msgstr ""
#: library/argparse.rst:758
msgid "choices_ - A container of the allowable values for the argument."
msgstr ""
#: library/argparse.rst:760
msgid ""
"required_ - Whether or not the command-line option may be omitted (optionals "
"only)."
msgstr ""
#: library/argparse.rst:763
msgid "help_ - A brief description of what the argument does."
msgstr ""
#: library/argparse.rst:765
msgid "metavar_ - A name for the argument in usage messages."
msgstr ""
#: library/argparse.rst:767
msgid ""
"dest_ - The name of the attribute to be added to the object returned by :"
"meth:`parse_args`."
msgstr ""
#: library/argparse.rst:776
msgid "name or flags"
msgstr ""
#: library/argparse.rst:778
msgid ""
"The :meth:`~ArgumentParser.add_argument` method must know whether an "
"optional argument, like ``-f`` or ``--foo``, or a positional argument, like "
"a list of filenames, is expected. The first arguments passed to :meth:"
"`~ArgumentParser.add_argument` must therefore be either a series of flags, "
"or a simple argument name."
msgstr ""
#: library/argparse.rst:784
msgid "For example, an optional argument could be created like::"
msgstr ""
#: library/argparse.rst:788
msgid "while a positional argument could be created like::"
msgstr ""
#: library/argparse.rst:792
msgid ""
"When :meth:`~ArgumentParser.parse_args` is called, optional arguments will "
"be identified by the ``-`` prefix, and the remaining arguments will be "
"assumed to be positional::"
msgstr ""
#: library/argparse.rst:811
msgid "action"
msgstr ""
#: library/argparse.rst:813
msgid ""
":class:`ArgumentParser` objects associate command-line arguments with "
"actions. These actions can do just about anything with the command-line "
"arguments associated with them, though most actions simply add an attribute "
"to the object returned by :meth:`~ArgumentParser.parse_args`. The "
"``action`` keyword argument specifies how the command-line arguments should "
"be handled. The supplied actions are:"
msgstr ""
#: library/argparse.rst:819
msgid ""
"``'store'`` - This just stores the argument's value. This is the default "
"action. For example::"
msgstr ""
#: library/argparse.rst:827
msgid ""
"``'store_const'`` - This stores the value specified by the const_ keyword "
"argument; note that the const_ keyword argument defaults to ``None``. The "
"``'store_const'`` action is most commonly used with optional arguments that "
"specify some sort of flag. For example::"
msgstr ""
#: library/argparse.rst:837
msgid ""
"``'store_true'`` and ``'store_false'`` - These are special cases of "
"``'store_const'`` used for storing the values ``True`` and ``False`` "
"respectively. In addition, they create default values of ``False`` and "
"``True`` respectively. For example::"
msgstr ""
#: library/argparse.rst:849
msgid ""
"``'append'`` - This stores a list, and appends each argument value to the "
"list. It is useful to allow an option to be specified multiple times. If the "
"default value is non-empty, the default elements will be present in the "
"parsed value for the option, with any values from the command line appended "
"after those default values. Example usage::"
msgstr ""
#: library/argparse.rst:860
msgid ""
"``'append_const'`` - This stores a list, and appends the value specified by "
"the const_ keyword argument to the list; note that the const_ keyword "
"argument defaults to ``None``. The ``'append_const'`` action is typically "
"useful when multiple arguments need to store constants to the same list. For "
"example::"
msgstr ""
#: library/argparse.rst:872
msgid ""
"``'count'`` - This counts the number of times a keyword argument occurs. For "
"example, this is useful for increasing verbosity levels::"
msgstr ""
#: library/argparse.rst:880
msgid "Note, the *default* will be ``None`` unless explicitly set to *0*."
msgstr ""
#: library/argparse.rst:882
msgid ""
"``'help'`` - This prints a complete help message for all the options in the "
"current parser and then exits. By default a help action is automatically "
"added to the parser. See :class:`ArgumentParser` for details of how the "
"output is created."
msgstr ""
#: library/argparse.rst:887
msgid ""
"``'version'`` - This expects a ``version=`` keyword argument in the :meth:"
"`~ArgumentParser.add_argument` call, and prints version information and "
"exits when invoked::"
msgstr ""
#: library/argparse.rst:897
msgid ""
"``'extend'`` - This stores a list, and extends each argument value to the "
"list. Example usage::"
msgstr ""
#: library/argparse.rst:908
msgid ""
"You may also specify an arbitrary action by passing an Action subclass or "
"other object that implements the same interface. The "
"``BooleanOptionalAction`` is available in ``argparse`` and adds support for "
"boolean actions such as ``--foo`` and ``--no-foo``::"
msgstr ""
#: library/argparse.rst:921
msgid ""
"The recommended way to create a custom action is to extend :class:`Action`, "
"overriding the ``__call__`` method and optionally the ``__init__`` and "
"``format_usage`` methods."
msgstr ""
#: library/argparse.rst:925
msgid "An example of a custom action::"
msgstr ""
#: library/argparse.rst:945
msgid "For more details, see :class:`Action`."
msgstr ""
#: library/argparse.rst:951
msgid "nargs"
msgstr ""
#: library/argparse.rst:953
msgid ""
"ArgumentParser objects usually associate a single command-line argument with "
"a single action to be taken. The ``nargs`` keyword argument associates a "
"different number of command-line arguments with a single action. The "
"supported values are:"
msgstr ""
#: library/argparse.rst:958
msgid ""
"``N`` (an integer). ``N`` arguments from the command line will be gathered "
"together into a list. For example::"
msgstr ""
#: library/argparse.rst:967
msgid ""
"Note that ``nargs=1`` produces a list of one item. This is different from "
"the default, in which the item is produced by itself."
msgstr ""
#: library/argparse.rst:972
msgid ""
"``'?'``. One argument will be consumed from the command line if possible, "
"and produced as a single item. If no command-line argument is present, the "
"value from default_ will be produced. Note that for optional arguments, "
"there is an additional case - the option string is present but not followed "
"by a command-line argument. In this case the value from const_ will be "
"produced. Some examples to illustrate this::"
msgstr ""
#: library/argparse.rst:989
msgid ""
"One of the more common uses of ``nargs='?'`` is to allow optional input and "
"output files::"
msgstr ""
#: library/argparse.rst:1006
msgid ""
"``'*'``. All command-line arguments present are gathered into a list. Note "
"that it generally doesn't make much sense to have more than one positional "
"argument with ``nargs='*'``, but multiple optional arguments with "
"``nargs='*'`` is possible. For example::"
msgstr ""
#: library/argparse.rst:1020
msgid ""
"``'+'``. Just like ``'*'``, all command-line args present are gathered into "
"a list. Additionally, an error message will be generated if there wasn't at "
"least one command-line argument present. For example::"
msgstr ""
#: library/argparse.rst:1032
msgid ""
"If the ``nargs`` keyword argument is not provided, the number of arguments "
"consumed is determined by the action_. Generally this means a single "
"command-line argument will be consumed and a single item (not a list) will "
"be produced."
msgstr ""
#: library/argparse.rst:1040
msgid "const"
msgstr ""
#: library/argparse.rst:1042
msgid ""
"The ``const`` argument of :meth:`~ArgumentParser.add_argument` is used to "
"hold constant values that are not read from the command line but are "
"required for the various :class:`ArgumentParser` actions. The two most "
"common uses of it are:"
msgstr ""
#: library/argparse.rst:1046
msgid ""
"When :meth:`~ArgumentParser.add_argument` is called with "
"``action='store_const'`` or ``action='append_const'``. These actions add "
"the ``const`` value to one of the attributes of the object returned by :meth:"
"`~ArgumentParser.parse_args`. See the action_ description for examples. If "
"``const`` is not provided to :meth:`~ArgumentParser.add_argument`, it will "
"receive a default value of ``None``."
msgstr ""
#: library/argparse.rst:1054
msgid ""