-
-
Notifications
You must be signed in to change notification settings - Fork 53
Expand file tree
/
Copy pathconfigparser.po
More file actions
1286 lines (1099 loc) · 45.3 KB
/
configparser.po
File metadata and controls
1286 lines (1099 loc) · 45.3 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
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2017, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2017.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-15 07:19+0900\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../Doc/library/configparser.rst:2
msgid ":mod:`configparser` --- Configuration file parser"
msgstr ""
#: ../Doc/library/configparser.rst:14
msgid "**Source code:** :source:`Lib/configparser.py`"
msgstr ""
#: ../Doc/library/configparser.rst:24
msgid ""
"This module provides the :class:`ConfigParser` class which implements a "
"basic configuration language which provides a structure similar to what's"
" found in Microsoft Windows INI files. You can use this to write Python "
"programs which can be customized by end users easily."
msgstr ""
#: ../Doc/library/configparser.rst:31
msgid ""
"This library does *not* interpret or write the value-type prefixes used "
"in the Windows Registry extended version of INI syntax."
msgstr ""
#: ../Doc/library/configparser.rst:38
msgid "Module :mod:`shlex`"
msgstr ""
#: ../Doc/library/configparser.rst:37
msgid ""
"Support for creating Unix shell-like mini-languages which can be used as "
"an alternate format for application configuration files."
msgstr ""
#: ../Doc/library/configparser.rst:41
msgid "Module :mod:`json`"
msgstr ""
#: ../Doc/library/configparser.rst:41
msgid ""
"The json module implements a subset of JavaScript syntax which can also "
"be used for this purpose."
msgstr ""
#: ../Doc/library/configparser.rst:51
msgid "Quick Start"
msgstr ""
#: ../Doc/library/configparser.rst:53
msgid "Let's take a very basic configuration file that looks like this:"
msgstr ""
#: ../Doc/library/configparser.rst:70
msgid ""
"The structure of INI files is described `in the following section "
"<#supported-ini-file-structure>`_. Essentially, the file consists of "
"sections, each of which contains keys with values. :mod:`configparser` "
"classes can read and write such files. Let's start by creating the above"
" configuration file programmatically."
msgstr ""
#: ../Doc/library/configparser.rst:94
msgid ""
"As you can see, we can treat a config parser much like a dictionary. "
"There are differences, `outlined later <#mapping-protocol-access>`_, but "
"the behavior is very close to what you would expect from a dictionary."
msgstr ""
#: ../Doc/library/configparser.rst:98
msgid ""
"Now that we have created and saved a configuration file, let's read it "
"back and explore the data it holds."
msgstr ""
#: ../Doc/library/configparser.rst:133
msgid ""
"As we can see above, the API is pretty straightforward. The only bit of "
"magic involves the ``DEFAULT`` section which provides default values for "
"all other sections [1]_. Note also that keys in sections are case-"
"insensitive and stored in lowercase [1]_."
msgstr ""
#: ../Doc/library/configparser.rst:140
msgid "Supported Datatypes"
msgstr ""
#: ../Doc/library/configparser.rst:142
msgid ""
"Config parsers do not guess datatypes of values in configuration files, "
"always storing them internally as strings. This means that if you need "
"other datatypes, you should convert on your own:"
msgstr ""
#: ../Doc/library/configparser.rst:153
msgid ""
"Since this task is so common, config parsers provide a range of handy "
"getter methods to handle integers, floats and booleans. The last one is "
"the most interesting because simply passing the value to ``bool()`` would"
" do no good since ``bool('False')`` is still ``True``. This is why "
"config parsers also provide :meth:`~ConfigParser.getboolean`. This "
"method is case-insensitive and recognizes Boolean values from "
"``'yes'``/``'no'``, ``'on'``/``'off'``, ``'true'``/``'false'`` and "
"``'1'``/``'0'`` [1]_. For example:"
msgstr ""
#: ../Doc/library/configparser.rst:170
msgid ""
"Apart from :meth:`~ConfigParser.getboolean`, config parsers also provide "
"equivalent :meth:`~ConfigParser.getint` and "
":meth:`~ConfigParser.getfloat` methods. You can register your own "
"converters and customize the provided ones. [1]_"
msgstr ""
#: ../Doc/library/configparser.rst:176
msgid "Fallback Values"
msgstr ""
#: ../Doc/library/configparser.rst:178
msgid ""
"As with a dictionary, you can use a section's :meth:`get` method to "
"provide fallback values:"
msgstr ""
#: ../Doc/library/configparser.rst:191
msgid ""
"Please note that default values have precedence over fallback values. For"
" instance, in our example the ``'CompressionLevel'`` key was specified "
"only in the ``'DEFAULT'`` section. If we try to get it from the section "
"``'topsecret.server.com'``, we will always get the default, even if we "
"specify a fallback:"
msgstr ""
#: ../Doc/library/configparser.rst:202
msgid ""
"One more thing to be aware of is that the parser-level :meth:`get` method"
" provides a custom, more complex interface, maintained for backwards "
"compatibility. When using this method, a fallback value can be provided "
"via the ``fallback`` keyword-only argument:"
msgstr ""
#: ../Doc/library/configparser.rst:213
msgid ""
"The same ``fallback`` argument can be used with the "
":meth:`~ConfigParser.getint`, :meth:`~ConfigParser.getfloat` and "
":meth:`~ConfigParser.getboolean` methods, for example:"
msgstr ""
#: ../Doc/library/configparser.rst:229
msgid "Supported INI File Structure"
msgstr ""
#: ../Doc/library/configparser.rst:231
msgid ""
"A configuration file consists of sections, each led by a ``[section]`` "
"header, followed by key/value entries separated by a specific string "
"(``=`` or ``:`` by default [1]_). By default, section names are case "
"sensitive but keys are not [1]_. Leading and trailing whitespace is "
"removed from keys and values. Values can be omitted, in which case the "
"key/value delimiter may also be left out. Values can also span multiple "
"lines, as long as they are indented deeper than the first line of the "
"value. Depending on the parser's mode, blank lines may be treated as "
"parts of multiline values or ignored."
msgstr ""
#: ../Doc/library/configparser.rst:240
msgid ""
"Configuration files may include comments, prefixed by specific characters"
" (``#`` and ``;`` by default [1]_). Comments may appear on their own on "
"an otherwise empty line, possibly indented. [1]_"
msgstr ""
#: ../Doc/library/configparser.rst:244 ../Doc/library/configparser.rst:307
msgid "For example:"
msgstr ""
#: ../Doc/library/configparser.rst:292
msgid "Interpolation of values"
msgstr ""
#: ../Doc/library/configparser.rst:294
msgid ""
"On top of the core functionality, :class:`ConfigParser` supports "
"interpolation. This means values can be preprocessed before returning "
"them from ``get()`` calls."
msgstr ""
#: ../Doc/library/configparser.rst:302
msgid ""
"The default implementation used by :class:`ConfigParser`. It enables "
"values to contain format strings which refer to other values in the same "
"section, or values in the special default section [1]_. Additional "
"default values can be provided on initialization."
msgstr ""
#: ../Doc/library/configparser.rst:319
#, python-format
msgid ""
"In the example above, :class:`ConfigParser` with *interpolation* set to "
"``BasicInterpolation()`` would resolve ``%(home_dir)s`` to the value of "
"``home_dir`` (``/Users`` in this case). ``%(my_dir)s`` in effect would "
"resolve to ``/Users/lumberjack``. All interpolations are done on demand "
"so keys used in the chain of references do not have to be specified in "
"any specific order in the configuration file."
msgstr ""
#: ../Doc/library/configparser.rst:326
#, python-format
msgid ""
"With ``interpolation`` set to ``None``, the parser would simply return "
"``%(my_dir)s/Pictures`` as the value of ``my_pictures`` and "
"``%(home_dir)s/lumberjack`` as the value of ``my_dir``."
msgstr ""
#: ../Doc/library/configparser.rst:334
msgid ""
"An alternative handler for interpolation which implements a more advanced"
" syntax, used for instance in ``zc.buildout``. Extended interpolation is"
" using ``${section:option}`` to denote a value from a foreign section. "
"Interpolation can span multiple levels. For convenience, if the "
"``section:`` part is omitted, interpolation defaults to the current "
"section (and possibly the default values from the special section)."
msgstr ""
#: ../Doc/library/configparser.rst:341
msgid ""
"For example, the configuration specified above with basic interpolation, "
"would look like this with extended interpolation:"
msgstr ""
#: ../Doc/library/configparser.rst:354
msgid "Values from other sections can be fetched as well:"
msgstr ""
#: ../Doc/library/configparser.rst:376
msgid "Mapping Protocol Access"
msgstr ""
#: ../Doc/library/configparser.rst:380
msgid ""
"Mapping protocol access is a generic name for functionality that enables "
"using custom objects as if they were dictionaries. In case of "
":mod:`configparser`, the mapping interface implementation is using the "
"``parser['section']['option']`` notation."
msgstr ""
#: ../Doc/library/configparser.rst:385
msgid ""
"``parser['section']`` in particular returns a proxy for the section's "
"data in the parser. This means that the values are not copied but they "
"are taken from the original parser on demand. What's even more important"
" is that when values are changed on a section proxy, they are actually "
"mutated in the original parser."
msgstr ""
#: ../Doc/library/configparser.rst:391
msgid ""
":mod:`configparser` objects behave as close to actual dictionaries as "
"possible. The mapping interface is complete and adheres to the "
":class:`~collections.abc.MutableMapping` ABC. However, there are a few "
"differences that should be taken into account:"
msgstr ""
#: ../Doc/library/configparser.rst:396
msgid ""
"By default, all keys in sections are accessible in a case-insensitive "
"manner [1]_. E.g. ``for option in parser[\"section\"]`` yields only "
"``optionxform``'ed option key names. This means lowercased keys by "
"default. At the same time, for a section that holds the key ``'a'``, "
"both expressions return ``True``::"
msgstr ""
#: ../Doc/library/configparser.rst:404
msgid ""
"All sections include ``DEFAULTSECT`` values as well which means that "
"``.clear()`` on a section may not leave the section visibly empty. This "
"is because default values cannot be deleted from the section (because "
"technically they are not there). If they are overridden in the section, "
"deleting causes the default value to be visible again. Trying to delete "
"a default value causes a :exc:`KeyError`."
msgstr ""
#: ../Doc/library/configparser.rst:411
msgid "``DEFAULTSECT`` cannot be removed from the parser:"
msgstr ""
#: ../Doc/library/configparser.rst:413
msgid "trying to delete it raises :exc:`ValueError`,"
msgstr ""
#: ../Doc/library/configparser.rst:415
msgid "``parser.clear()`` leaves it intact,"
msgstr ""
#: ../Doc/library/configparser.rst:417
msgid "``parser.popitem()`` never returns it."
msgstr ""
#: ../Doc/library/configparser.rst:419
msgid ""
"``parser.get(section, option, **kwargs)`` - the second argument is "
"**not** a fallback value. Note however that the section-level ``get()`` "
"methods are compatible both with the mapping protocol and the classic "
"configparser API."
msgstr ""
#: ../Doc/library/configparser.rst:423
msgid ""
"``parser.items()`` is compatible with the mapping protocol (returns a "
"list of *section_name*, *section_proxy* pairs including the DEFAULTSECT)."
" However, this method can also be invoked with arguments: "
"``parser.items(section, raw, vars)``. The latter call returns a list of "
"*option*, *value* pairs for a specified ``section``, with all "
"interpolations expanded (unless ``raw=True`` is provided)."
msgstr ""
#: ../Doc/library/configparser.rst:430
msgid ""
"The mapping protocol is implemented on top of the existing legacy API so "
"that subclasses overriding the original interface still should have "
"mappings working as expected."
msgstr ""
#: ../Doc/library/configparser.rst:436
msgid "Customizing Parser Behaviour"
msgstr ""
#: ../Doc/library/configparser.rst:438
msgid ""
"There are nearly as many INI format variants as there are applications "
"using it. :mod:`configparser` goes a long way to provide support for the "
"largest sensible set of INI styles available. The default functionality "
"is mainly dictated by historical background and it's very likely that you"
" will want to customize some of the features."
msgstr ""
#: ../Doc/library/configparser.rst:444
msgid ""
"The most common way to change the way a specific config parser works is "
"to use the :meth:`__init__` options:"
msgstr ""
#: ../Doc/library/configparser.rst:447
msgid "*defaults*, default value: ``None``"
msgstr ""
#: ../Doc/library/configparser.rst:449
msgid ""
"This option accepts a dictionary of key-value pairs which will be "
"initially put in the ``DEFAULT`` section. This makes for an elegant way "
"to support concise configuration files that don't specify values which "
"are the same as the documented default."
msgstr ""
#: ../Doc/library/configparser.rst:454
msgid ""
"Hint: if you want to specify default values for a specific section, use "
":meth:`read_dict` before you read the actual file."
msgstr ""
#: ../Doc/library/configparser.rst:457
msgid "*dict_type*, default value: :class:`dict`"
msgstr ""
#: ../Doc/library/configparser.rst:459
msgid ""
"This option has a major impact on how the mapping protocol will behave "
"and how the written configuration files look. With the standard "
"dictionary, every section is stored in the order they were added to the "
"parser. Same goes for options within sections."
msgstr ""
#: ../Doc/library/configparser.rst:464
msgid ""
"An alternative dictionary type can be used for example to sort sections "
"and options on write-back."
msgstr ""
#: ../Doc/library/configparser.rst:467
msgid ""
"Please note: there are ways to add a set of key-value pairs in a single "
"operation. When you use a regular dictionary in those operations, the "
"order of the keys will be ordered. For example:"
msgstr ""
#: ../Doc/library/configparser.rst:489
msgid "*allow_no_value*, default value: ``False``"
msgstr ""
#: ../Doc/library/configparser.rst:491
msgid ""
"Some configuration files are known to include settings without values, "
"but which otherwise conform to the syntax supported by "
":mod:`configparser`. The *allow_no_value* parameter to the constructor "
"can be used to indicate that such values should be accepted:"
msgstr ""
#: ../Doc/library/configparser.rst:526
msgid "*delimiters*, default value: ``('=', ':')``"
msgstr ""
#: ../Doc/library/configparser.rst:528
msgid ""
"Delimiters are substrings that delimit keys from values within a section."
" The first occurrence of a delimiting substring on a line is considered a"
" delimiter. This means values (but not keys) can contain the delimiters."
msgstr ""
#: ../Doc/library/configparser.rst:532
msgid ""
"See also the *space_around_delimiters* argument to "
":meth:`ConfigParser.write`."
msgstr ""
#: ../Doc/library/configparser.rst:535
msgid "*comment_prefixes*, default value: ``('#', ';')``"
msgstr ""
#: ../Doc/library/configparser.rst:537
msgid "*inline_comment_prefixes*, default value: ``None``"
msgstr ""
#: ../Doc/library/configparser.rst:539
msgid ""
"Comment prefixes are strings that indicate the start of a valid comment "
"within a config file. *comment_prefixes* are used only on otherwise empty"
" lines (optionally indented) whereas *inline_comment_prefixes* can be "
"used after every valid value (e.g. section names, options and empty lines"
" as well). By default inline comments are disabled and ``'#'`` and "
"``';'`` are used as prefixes for whole line comments."
msgstr ""
#: ../Doc/library/configparser.rst:546
msgid ""
"In previous versions of :mod:`configparser` behaviour matched "
"``comment_prefixes=('#',';')`` and ``inline_comment_prefixes=(';',)``."
msgstr ""
#: ../Doc/library/configparser.rst:550
msgid ""
"Please note that config parsers don't support escaping of comment "
"prefixes so using *inline_comment_prefixes* may prevent users from "
"specifying option values with characters used as comment prefixes. When "
"in doubt, avoid setting *inline_comment_prefixes*. In any circumstances,"
" the only way of storing comment prefix characters at the beginning of a "
"line in multiline values is to interpolate the prefix, for example::"
msgstr ""
#: ../Doc/library/configparser.rst:596
msgid "*strict*, default value: ``True``"
msgstr ""
#: ../Doc/library/configparser.rst:598
msgid ""
"When set to ``True``, the parser will not allow for any section or option"
" duplicates while reading from a single source (using :meth:`read_file`, "
":meth:`read_string` or :meth:`read_dict`). It is recommended to use "
"strict parsers in new applications."
msgstr ""
#: ../Doc/library/configparser.rst:603
msgid ""
"In previous versions of :mod:`configparser` behaviour matched "
"``strict=False``."
msgstr ""
#: ../Doc/library/configparser.rst:607
msgid "*empty_lines_in_values*, default value: ``True``"
msgstr ""
#: ../Doc/library/configparser.rst:609
msgid ""
"In config parsers, values can span multiple lines as long as they are "
"indented more than the key that holds them. By default parsers also let "
"empty lines to be parts of values. At the same time, keys can be "
"arbitrarily indented themselves to improve readability. In consequence, "
"when configuration files get big and complex, it is easy for the user to "
"lose track of the file structure. Take for instance:"
msgstr ""
#: ../Doc/library/configparser.rst:624
msgid ""
"This can be especially problematic for the user to see if she's using a "
"proportional font to edit the file. That is why when your application "
"does not need values with empty lines, you should consider disallowing "
"them. This will make empty lines split keys every time. In the example "
"above, it would produce two keys, ``key`` and ``this``."
msgstr ""
#: ../Doc/library/configparser.rst:630
msgid ""
"*default_section*, default value: ``configparser.DEFAULTSECT`` (that is: "
"``\"DEFAULT\"``)"
msgstr ""
#: ../Doc/library/configparser.rst:633
msgid ""
"The convention of allowing a special section of default values for other "
"sections or interpolation purposes is a powerful concept of this library,"
" letting users create complex declarative configurations. This section "
"is normally called ``\"DEFAULT\"`` but this can be customized to point to"
" any other valid section name. Some typical values include: "
"``\"general\"`` or ``\"common\"``. The name provided is used for "
"recognizing default sections when reading from any source and is used "
"when writing configuration back to a file. Its current value can be "
"retrieved using the ``parser_instance.default_section`` attribute and may"
" be modified at runtime (i.e. to convert files from one format to "
"another)."
msgstr ""
#: ../Doc/library/configparser.rst:644
msgid "*interpolation*, default value: ``configparser.BasicInterpolation``"
msgstr ""
#: ../Doc/library/configparser.rst:646
msgid ""
"Interpolation behaviour may be customized by providing a custom handler "
"through the *interpolation* argument. ``None`` can be used to turn off "
"interpolation completely, ``ExtendedInterpolation()`` provides a more "
"advanced variant inspired by ``zc.buildout``. More on the subject in the"
" `dedicated documentation section <#interpolation-of-values>`_. "
":class:`RawConfigParser` has a default value of ``None``."
msgstr ""
#: ../Doc/library/configparser.rst:653
msgid "*converters*, default value: not set"
msgstr ""
#: ../Doc/library/configparser.rst:655
msgid ""
"Config parsers provide option value getters that perform type conversion."
" By default :meth:`~ConfigParser.getint`, "
":meth:`~ConfigParser.getfloat`, and :meth:`~ConfigParser.getboolean` are "
"implemented. Should other getters be desirable, users may define them in"
" a subclass or pass a dictionary where each key is a name of the "
"converter and each value is a callable implementing said conversion. For"
" instance, passing ``{'decimal': decimal.Decimal}`` would add "
":meth:`getdecimal` on both the parser object and all section proxies. In"
" other words, it will be possible to write both "
"``parser_instance.getdecimal('section', 'key', fallback=0)`` and "
"``parser_instance['section'].getdecimal('key', 0)``."
msgstr ""
#: ../Doc/library/configparser.rst:666
msgid ""
"If the converter needs to access the state of the parser, it can be "
"implemented as a method on a config parser subclass. If the name of this"
" method starts with ``get``, it will be available on all section proxies,"
" in the dict-compatible form (see the ``getdecimal()`` example above)."
msgstr ""
#: ../Doc/library/configparser.rst:671
msgid ""
"More advanced customization may be achieved by overriding default values "
"of these parser attributes. The defaults are defined on the classes, so "
"they may be overridden by subclasses or by attribute assignment."
msgstr ""
#: ../Doc/library/configparser.rst:677
msgid ""
"By default when using :meth:`~ConfigParser.getboolean`, config parsers "
"consider the following values ``True``: ``'1'``, ``'yes'``, ``'true'``, "
"``'on'`` and the following values ``False``: ``'0'``, ``'no'``, "
"``'false'``, ``'off'``. You can override this by specifying a custom "
"dictionary of strings and their Boolean outcomes. For example:"
msgstr ""
#: ../Doc/library/configparser.rst:695
msgid ""
"Other typical Boolean pairs include ``accept``/``reject`` or "
"``enabled``/``disabled``."
msgstr ""
#: ../Doc/library/configparser.rst:700
msgid ""
"This method transforms option names on every read, get, or set operation."
" The default converts the name to lowercase. This also means that when "
"a configuration file gets written, all keys will be lowercase. Override "
"this method if that's unsuitable. For example:"
msgstr ""
#: ../Doc/library/configparser.rst:730
msgid ""
"The optionxform function transforms option names to a canonical form. "
"This should be an idempotent function: if the name is already in "
"canonical form, it should be returned unchanged."
msgstr ""
#: ../Doc/library/configparser.rst:737
msgid ""
"A compiled regular expression used to parse section headers. The default"
" matches ``[section]`` to the name ``\"section\"``. Whitespace is "
"considered part of the section name, thus ``[ larch ]`` will be read as"
" a section of name ``\" larch \"``. Override this attribute if that's "
"unsuitable. For example:"
msgstr ""
#: ../Doc/library/configparser.rst:765
msgid ""
"While ConfigParser objects also use an ``OPTCRE`` attribute for "
"recognizing option lines, it's not recommended to override it because "
"that would interfere with constructor options *allow_no_value* and "
"*delimiters*."
msgstr ""
#: ../Doc/library/configparser.rst:771
msgid "Legacy API Examples"
msgstr ""
#: ../Doc/library/configparser.rst:773
msgid ""
"Mainly because of backwards compatibility concerns, :mod:`configparser` "
"provides also a legacy API with explicit ``get``/``set`` methods. While "
"there are valid use cases for the methods outlined below, mapping "
"protocol access is preferred for new projects. The legacy API is at "
"times more advanced, low-level and downright counterintuitive."
msgstr ""
#: ../Doc/library/configparser.rst:779
msgid "An example of writing to a configuration file::"
msgstr ""
#: ../Doc/library/configparser.rst:802
msgid "An example of reading the configuration file again::"
msgstr ""
#: ../Doc/library/configparser.rst:820
msgid "To get interpolation, use :class:`ConfigParser`::"
msgstr ""
#: ../Doc/library/configparser.rst:853
msgid ""
"Default values are available in both types of ConfigParsers. They are "
"used in interpolation if an option used is not defined elsewhere. ::"
msgstr ""
#: ../Doc/library/configparser.rst:871
msgid "ConfigParser Objects"
msgstr ""
#: ../Doc/library/configparser.rst:875
msgid ""
"The main configuration parser. When *defaults* is given, it is "
"initialized into the dictionary of intrinsic defaults. When *dict_type* "
"is given, it will be used to create the dictionary objects for the list "
"of sections, for the options within a section, and for the default "
"values."
msgstr ""
#: ../Doc/library/configparser.rst:880
msgid ""
"When *delimiters* is given, it is used as the set of substrings that "
"divide keys from values. When *comment_prefixes* is given, it will be "
"used as the set of substrings that prefix comments in otherwise empty "
"lines. Comments can be indented. When *inline_comment_prefixes* is "
"given, it will be used as the set of substrings that prefix comments in "
"non-empty lines."
msgstr ""
#: ../Doc/library/configparser.rst:886
msgid ""
"When *strict* is ``True`` (the default), the parser won't allow for any "
"section or option duplicates while reading from a single source (file, "
"string or dictionary), raising :exc:`DuplicateSectionError` or "
":exc:`DuplicateOptionError`. When *empty_lines_in_values* is ``False`` "
"(default: ``True``), each empty line marks the end of an option. "
"Otherwise, internal empty lines of a multiline option are kept as part of"
" the value. When *allow_no_value* is ``True`` (default: ``False``), "
"options without values are accepted; the value held for these is ``None``"
" and they are serialized without the trailing delimiter."
msgstr ""
#: ../Doc/library/configparser.rst:896
msgid ""
"When *default_section* is given, it specifies the name for the special "
"section holding default values for other sections and interpolation "
"purposes (normally named ``\"DEFAULT\"``). This value can be retrieved "
"and changed on runtime using the ``default_section`` instance attribute."
msgstr ""
#: ../Doc/library/configparser.rst:901
msgid ""
"Interpolation behaviour may be customized by providing a custom handler "
"through the *interpolation* argument. ``None`` can be used to turn off "
"interpolation completely, ``ExtendedInterpolation()`` provides a more "
"advanced variant inspired by ``zc.buildout``. More on the subject in the"
" `dedicated documentation section <#interpolation-of-values>`_."
msgstr ""
#: ../Doc/library/configparser.rst:907
#, python-format
msgid ""
"All option names used in interpolation will be passed through the "
":meth:`optionxform` method just like any other option name reference. "
"For example, using the default implementation of :meth:`optionxform` "
"(which converts option names to lower case), the values ``foo %(bar)s`` "
"and ``foo %(BAR)s`` are equivalent."
msgstr ""
#: ../Doc/library/configparser.rst:913
msgid ""
"When *converters* is given, it should be a dictionary where each key "
"represents the name of a type converter and each value is a callable "
"implementing the conversion from string to the desired datatype. Every "
"converter gets its own corresponding :meth:`get*()` method on the parser "
"object and section proxies."
msgstr ""
#: ../Doc/library/configparser.rst:919
msgid "The default *dict_type* is :class:`collections.OrderedDict`."
msgstr ""
#: ../Doc/library/configparser.rst:922
msgid ""
"*allow_no_value*, *delimiters*, *comment_prefixes*, *strict*, "
"*empty_lines_in_values*, *default_section* and *interpolation* were "
"added."
msgstr ""
#: ../Doc/library/configparser.rst:927
msgid "The *converters* argument was added."
msgstr ""
#: ../Doc/library/configparser.rst:930
msgid ""
"The *defaults* argument is read with :meth:`read_dict()`, providing "
"consistent behavior across the parser: non-string keys and values are "
"implicitly converted to strings."
msgstr ""
#: ../Doc/library/configparser.rst:935 ../Doc/library/configparser.rst:1213
msgid ""
"The default *dict_type* is :class:`dict`, since it now preserves "
"insertion order."
msgstr ""
#: ../Doc/library/configparser.rst:941
msgid "Return a dictionary containing the instance-wide defaults."
msgstr ""
#: ../Doc/library/configparser.rst:946
msgid ""
"Return a list of the sections available; the *default section* is not "
"included in the list."
msgstr ""
#: ../Doc/library/configparser.rst:952
msgid ""
"Add a section named *section* to the instance. If a section by the given"
" name already exists, :exc:`DuplicateSectionError` is raised. If the "
"*default section* name is passed, :exc:`ValueError` is raised. The name "
"of the section must be a string; if not, :exc:`TypeError` is raised."
msgstr ""
#: ../Doc/library/configparser.rst:957
msgid "Non-string section names raise :exc:`TypeError`."
msgstr ""
#: ../Doc/library/configparser.rst:963
msgid ""
"Indicates whether the named *section* is present in the configuration. "
"The *default section* is not acknowledged."
msgstr ""
#: ../Doc/library/configparser.rst:969
msgid "Return a list of options available in the specified *section*."
msgstr ""
#: ../Doc/library/configparser.rst:974
msgid ""
"If the given *section* exists, and contains the given *option*, return "
":const:`True`; otherwise return :const:`False`. If the specified "
"*section* is :const:`None` or an empty string, DEFAULT is assumed."
msgstr ""
#: ../Doc/library/configparser.rst:981
msgid ""
"Attempt to read and parse an iterable of filenames, returning a list of "
"filenames which were successfully parsed."
msgstr ""
#: ../Doc/library/configparser.rst:984
msgid ""
"If *filenames* is a string, a :class:`bytes` object or a :term:`path-like"
" object`, it is treated as a single filename. If a file named in "
"*filenames* cannot be opened, that file will be ignored. This is "
"designed so that you can specify an iterable of potential configuration "
"file locations (for example, the current directory, the user's home "
"directory, and some system-wide directory), and all existing "
"configuration files in the iterable will be read."
msgstr ""
#: ../Doc/library/configparser.rst:993
msgid ""
"If none of the named files exist, the :class:`ConfigParser` instance will"
" contain an empty dataset. An application which requires initial values "
"to be loaded from a file should load the required file or files using "
":meth:`read_file` before calling :meth:`read` for any optional files::"
msgstr ""
#: ../Doc/library/configparser.rst:1006
msgid ""
"The *encoding* parameter. Previously, all files were read using the "
"default encoding for :func:`open`."
msgstr ""
#: ../Doc/library/configparser.rst:1010
msgid "The *filenames* parameter accepts a :term:`path-like object`."
msgstr ""
#: ../Doc/library/configparser.rst:1013
msgid "The *filenames* parameter accepts a :class:`bytes` object."
msgstr ""
#: ../Doc/library/configparser.rst:1019
msgid ""
"Read and parse configuration data from *f* which must be an iterable "
"yielding Unicode strings (for example files opened in text mode)."
msgstr ""
#: ../Doc/library/configparser.rst:1022
msgid ""
"Optional argument *source* specifies the name of the file being read. If"
" not given and *f* has a :attr:`name` attribute, that is used for "
"*source*; the default is ``'<???>'``."
msgstr ""
#: ../Doc/library/configparser.rst:1026
msgid "Replaces :meth:`readfp`."
msgstr ""
#: ../Doc/library/configparser.rst:1031
msgid "Parse configuration data from a string."
msgstr ""
#: ../Doc/library/configparser.rst:1033
msgid ""
"Optional argument *source* specifies a context-specific name of the "
"string passed. If not given, ``'<string>'`` is used. This should "
"commonly be a filesystem path or a URL."
msgstr ""
#: ../Doc/library/configparser.rst:1042
msgid ""
"Load configuration from any object that provides a dict-like ``items()`` "
"method. Keys are section names, values are dictionaries with keys and "
"values that should be present in the section. If the used dictionary "
"type preserves order, sections and their keys will be added in order. "
"Values are automatically converted to strings."
msgstr ""
#: ../Doc/library/configparser.rst:1048
msgid ""
"Optional argument *source* specifies a context-specific name of the "
"dictionary passed. If not given, ``<dict>`` is used."
msgstr ""
#: ../Doc/library/configparser.rst:1051
msgid "This method can be used to copy state between parsers."
msgstr ""
#: ../Doc/library/configparser.rst:1058
msgid ""
"Get an *option* value for the named *section*. If *vars* is provided, it"
" must be a dictionary. The *option* is looked up in *vars* (if "
"provided), *section*, and in *DEFAULTSECT* in that order. If the key is "
"not found and *fallback* is provided, it is used as a fallback value. "
"``None`` can be provided as a *fallback* value."
msgstr ""
#: ../Doc/library/configparser.rst:1064
msgid ""
"All the ``'%'`` interpolations are expanded in the return values, unless "
"the *raw* argument is true. Values for interpolation keys are looked up "
"in the same manner as the option."
msgstr ""
#: ../Doc/library/configparser.rst:1068
msgid ""
"Arguments *raw*, *vars* and *fallback* are keyword only to protect users "
"from trying to use the third argument as the *fallback* fallback "
"(especially when using the mapping protocol)."
msgstr ""
#: ../Doc/library/configparser.rst:1076
msgid ""
"A convenience method which coerces the *option* in the specified "
"*section* to an integer. See :meth:`get` for explanation of *raw*, "
"*vars* and *fallback*."
msgstr ""
#: ../Doc/library/configparser.rst:1083
msgid ""
"A convenience method which coerces the *option* in the specified "
"*section* to a floating point number. See :meth:`get` for explanation of"
" *raw*, *vars* and *fallback*."
msgstr ""
#: ../Doc/library/configparser.rst:1090
msgid ""
"A convenience method which coerces the *option* in the specified "
"*section* to a Boolean value. Note that the accepted values for the "
"option are ``'1'``, ``'yes'``, ``'true'``, and ``'on'``, which cause this"
" method to return ``True``, and ``'0'``, ``'no'``, ``'false'``, and "
"``'off'``, which cause it to return ``False``. These string values are "
"checked in a case-insensitive manner. Any other value will cause it to "
"raise :exc:`ValueError`. See :meth:`get` for explanation of *raw*, "
"*vars* and *fallback*."
msgstr ""
#: ../Doc/library/configparser.rst:1103
msgid ""
"When *section* is not given, return a list of *section_name*, "
"*section_proxy* pairs, including DEFAULTSECT."
msgstr ""
#: ../Doc/library/configparser.rst:1106
msgid ""
"Otherwise, return a list of *name*, *value* pairs for the options in the "
"given *section*. Optional arguments have the same meaning as for the "
":meth:`get` method."
msgstr ""
#: ../Doc/library/configparser.rst:1110
msgid ""
"Items present in *vars* no longer appear in the result. The previous "
"behaviour mixed actual parser options with variables provided for "
"interpolation."
msgstr ""
#: ../Doc/library/configparser.rst:1118
msgid ""
"If the given section exists, set the given option to the specified value;"
" otherwise raise :exc:`NoSectionError`. *option* and *value* must be "
"strings; if not, :exc:`TypeError` is raised."
msgstr ""
#: ../Doc/library/configparser.rst:1125
msgid ""
"Write a representation of the configuration to the specified :term:`file "
"object`, which must be opened in text mode (accepting strings). This "
"representation can be parsed by a future :meth:`read` call. If "
"*space_around_delimiters* is true, delimiters between keys and values are"
" surrounded by spaces."
msgstr ""
#: ../Doc/library/configparser.rst:1134
msgid ""
"Remove the specified *option* from the specified *section*. If the "
"section does not exist, raise :exc:`NoSectionError`. If the option "
"existed to be removed, return :const:`True`; otherwise return "
":const:`False`."
msgstr ""
#: ../Doc/library/configparser.rst:1142
msgid ""
"Remove the specified *section* from the configuration. If the section in"
" fact existed, return ``True``. Otherwise return ``False``."
msgstr ""
#: ../Doc/library/configparser.rst:1148
msgid ""
"Transforms the option name *option* as found in an input file or as "
"passed in by client code to the form that should be used in the internal "
"structures. The default implementation returns a lower-case version of "
"*option*; subclasses may override this or client code can set an "
"attribute of this name on instances to affect this behavior."
msgstr ""
#: ../Doc/library/configparser.rst:1154
msgid ""
"You don't need to subclass the parser to use this method, you can also "
"set it on an instance, to a function that takes a string argument and "
"returns a string. Setting it to ``str``, for example, would make option "
"names case sensitive::"
msgstr ""
#: ../Doc/library/configparser.rst:1162
msgid ""
"Note that when reading configuration files, whitespace around the option "
"names is stripped before :meth:`optionxform` is called."
msgstr ""
#: ../Doc/library/configparser.rst:1168