GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — python-docs-ru/library/configparser.po at 3.14 · python/python-docs-ru Expand file tree/ Copy pathconfigparser.poMore file actions 1597 lines (1370 loc) · 52.3 KB / Copy pathconfigparser.poFile metadata and controls1597 lines (1370 loc) · 52.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 Python Software Foundation # This file is distributed under the same license as the Python package. # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. # # Translators: # python-doc bot, 2025 # Dmitry Luschan, 2025 # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Python 3.15\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2026-11-03 20:20+0000\n" "PO-Revision-Date: 2025-09-16 00:01+0000\n" "Last-Translator: Dmitry Luschan, 2025\n" "Language-Team: Russian (https://app.transifex.com/python-doc/teams/5390/" "ru/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: ru\n" "Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && " "n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || " "(n%100>=11 && n%100<=14)? 2 : 3);\n" msgid ":mod:`!configparser` --- Configuration file parser" msgstr "" msgid "**Source code:** :source:`Lib/configparser.py`" msgstr "" 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 "" msgid "" "This library does *not* interpret or write the value-type prefixes used in " "the Windows Registry extended version of INI syntax." msgstr "" msgid "" "Be cautious when parsing data from untrusted sources. A malicious INI file " "may cause the decoder to consume considerable CPU and memory resources. " "Limiting the size of data to be parsed is recommended." msgstr "" msgid "Module :mod:`tomllib`" msgstr "" msgid "" "TOML is a well-specified format for application configuration files. It is " "specifically designed to be an improved version of INI." msgstr "" msgid "Module :mod:`shlex`" msgstr "" msgid "" "Support for creating Unix shell-like mini-languages which can also be used " "for application configuration files." msgstr "" msgid "Module :mod:`json`" msgstr "" msgid "" "The ``json`` module implements a subset of JavaScript syntax which is " "sometimes used for configuration, but does not support comments." msgstr "" msgid "Quick Start" msgstr "" msgid "Let's take a very basic configuration file that looks like this:" msgstr "" msgid "" "[DEFAULT]\n" "ServerAliveInterval = 45\n" "Compression = yes\n" "CompressionLevel = 9\n" "ForwardX11 = yes\n" "\n" "[forge.example]\n" "User = hg\n" "\n" "[topsecret.server.example]\n" "Port = 50022\n" "ForwardX11 = no" msgstr "" 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 "" msgid "" ">>> import configparser\n" ">>> config = configparser.ConfigParser()\n" ">>> config['DEFAULT'] = {'ServerAliveInterval': '45',\n" "... 'Compression': 'yes',\n" "... 'CompressionLevel': '9'}\n" ">>> config['forge.example'] = {}\n" ">>> config['forge.example']['User'] = 'hg'\n" ">>> config['topsecret.server.example'] = {}\n" ">>> topsecret = config['topsecret.server.example']\n" ">>> topsecret['Port'] = '50022' # mutates the parser\n" ">>> topsecret['ForwardX11'] = 'no' # same here\n" ">>> config['DEFAULT']['ForwardX11'] = 'yes'\n" ">>> with open('example.ini', 'w') as configfile:\n" "... config.write(configfile)\n" "..." msgstr "" 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 "" msgid "" "Now that we have created and saved a configuration file, let's read it back " "and explore the data it holds." msgstr "" msgid "" ">>> config = configparser.ConfigParser()\n" ">>> config.sections()\n" "[]\n" ">>> config.read('example.ini')\n" "['example.ini']\n" ">>> config.sections()\n" "['forge.example', 'topsecret.server.example']\n" ">>> 'forge.example' in config\n" "True\n" ">>> 'python.org' in config\n" "False\n" ">>> config['forge.example']['User']\n" "'hg'\n" ">>> config['DEFAULT']['Compression']\n" "'yes'\n" ">>> topsecret = config['topsecret.server.example']\n" ">>> topsecret['ForwardX11']\n" "'no'\n" ">>> topsecret['Port']\n" "'50022'\n" ">>> for key in config['forge.example']:\n" "... print(key)\n" "user\n" "compressionlevel\n" "serveraliveinterval\n" "compression\n" "forwardx11\n" ">>> config['forge.example']['ForwardX11']\n" "'yes'" msgstr "" 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 "" msgid "" "It is possible to read several configurations into a " "single :class:`ConfigParser`, where the most recently added configuration " "has the highest priority. Any conflicting keys are taken from the more " "recent configuration while the previously existing keys are retained. The " "example below reads in an ``override.ini`` file, which will override any " "conflicting keys from the ``example.ini`` file." msgstr "" msgid "" "[DEFAULT]\n" "ServerAliveInterval = -1" msgstr "" msgid "" ">>> config_override = configparser.ConfigParser()\n" ">>> config_override['DEFAULT'] = {'ServerAliveInterval': '-1'}\n" ">>> with open('override.ini', 'w') as configfile:\n" "... config_override.write(configfile)\n" "...\n" ">>> config_override = configparser.ConfigParser()\n" ">>> config_override.read(['example.ini', 'override.ini'])\n" "['example.ini', 'override.ini']\n" ">>> print(config_override.get('DEFAULT', 'ServerAliveInterval'))\n" "-1" msgstr "" msgid "" "This behaviour is equivalent to a :meth:`ConfigParser.read` call with " "several files passed to the *filenames* parameter." msgstr "" msgid "Supported Datatypes" msgstr "" 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 "" msgid "" ">>> int(topsecret['Port'])\n" "50022\n" ">>> float(topsecret['CompressionLevel'])\n" "9.0" msgstr "" 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 "" msgid "" ">>> topsecret.getboolean('ForwardX11')\n" "False\n" ">>> config['forge.example'].getboolean('ForwardX11')\n" "True\n" ">>> config.getboolean('forge.example', 'Compression')\n" "True" msgstr "" 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 "" msgid "Fallback Values" msgstr "" msgid "" "As with a dictionary, you can use a section's :meth:`~ConfigParser.get` " "method to provide fallback values:" msgstr "" msgid "" ">>> topsecret.get('Port')\n" "'50022'\n" ">>> topsecret.get('CompressionLevel')\n" "'9'\n" ">>> topsecret.get('Cipher')\n" ">>> topsecret.get('Cipher', '3des-cbc')\n" "'3des-cbc'" msgstr "" 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.example'``, we will always get the default, even if we " "specify a fallback:" msgstr "" msgid "" ">>> topsecret.get('CompressionLevel', '3')\n" "'9'" msgstr "" msgid "" "One more thing to be aware of is that the parser-" "level :meth:`~ConfigParser.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 "" msgid "" ">>> config.get('forge.example', 'monster',\n" "... fallback='No such things as monsters')\n" "'No such things as monsters'" msgstr "" msgid "" "The same ``fallback`` argument can be used with " "the :meth:`~ConfigParser.getint`, :meth:`~ConfigParser.getfloat` " "and :meth:`~ConfigParser.getboolean` methods, for example:" msgstr "" msgid "" ">>> 'BatchMode' in topsecret\n" "False\n" ">>> topsecret.getboolean('BatchMode', fallback=True)\n" "True\n" ">>> config['DEFAULT']['BatchMode'] = 'no'\n" ">>> topsecret.getboolean('BatchMode', fallback=True)\n" "False" msgstr "" msgid "Supported INI File Structure" msgstr "" 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 if the parser is configured to allow it [1]_, " "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 "" msgid "" "By default, a valid section name can be any string that does not contain '\\" "\\n'. To change this, see :attr:`ConfigParser.SECTCRE`." msgstr "" msgid "" "The first section name may be omitted if the parser is configured to allow " "an unnamed top level section with ``allow_unnamed_section=True``. In this " "case, the keys/values may be retrieved by :const:`UNNAMED_SECTION` as in " "``config[UNNAMED_SECTION]``." msgstr "" 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 "" msgid "For example:" msgstr "" msgid "" "[Simple Values]\n" "key=value\n" "spaces in keys=allowed\n" "spaces in values=allowed as well\n" "spaces around the delimiter = obviously\n" "you can also use : to delimit keys from values\n" "\n" "[All Values Are Strings]\n" "values like this: 1000000\n" "or this: 3.14159265359\n" "are they treated as numbers? : no\n" "integers, floats and booleans are held as: strings\n" "can use the API to get converted values directly: true\n" "\n" "[Multiline Values]\n" "chorus: I'm a lumberjack, and I'm okay\n" " I sleep all night and I work all day\n" "\n" "[No Values]\n" "key_without_value\n" "empty string value here =\n" "\n" "[You can use comments]\n" "# like this\n" "; or this\n" "\n" "# By default only in an empty line.\n" "# Inline comments can be harmful because they prevent users\n" "# from using the delimiting characters as parts of values.\n" "# That being said, this can be customized.\n" "\n" " [Sections Can Be Indented]\n" " can_values_be_as_well = True\n" " does_that_mean_anything_special = False\n" " purpose = formatting for readability\n" " multiline_values = are\n" " handled just fine as\n" " long as they are indented\n" " deeper than the first line\n" " of a value\n" " # Did I mention we can indent comments, too?" msgstr "" msgid "Unnamed Sections" msgstr "" msgid "" "The name of the first section (or unique) may be omitted and values " "retrieved by the :const:`UNNAMED_SECTION` attribute." msgstr "" msgid "" ">>> config = \"\"\"\n" "... option = value\n" "...\n" "... [ Section 2 ]\n" "... another = val\n" "... \"\"\"\n" ">>> unnamed = configparser.ConfigParser(allow_unnamed_section=True)\n" ">>> unnamed.read_string(config)\n" ">>> unnamed.get(configparser.UNNAMED_SECTION, 'option')\n" "'value'" msgstr "" msgid "Interpolation of values" msgstr "" msgid "" "On top of the core functionality, :class:`ConfigParser` supports " "interpolation. This means values can be preprocessed before returning them " "from ``get()`` calls." msgstr "" 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 "" msgid "" "[Paths]\n" "home_dir: /Users\n" "my_dir: %(home_dir)s/lumberjack\n" "my_pictures: %(my_dir)s/Pictures\n" "\n" "[Escape]\n" "# use a %% to escape the % sign (% is the only character that needs to be " "escaped):\n" "gain: 80%%" msgstr "" 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 "" 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 "" 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 "" msgid "" "For example, the configuration specified above with basic interpolation, " "would look like this with extended interpolation:" msgstr "" msgid "" "[Paths]\n" "home_dir: /Users\n" "my_dir: ${home_dir}/lumberjack\n" "my_pictures: ${my_dir}/Pictures\n" "\n" "[Escape]\n" "# use a $$ to escape the $ sign ($ is the only character that needs to be " "escaped):\n" "cost: $$80" msgstr "" msgid "Values from other sections can be fetched as well:" msgstr "" msgid "" "[Common]\n" "home_dir: /Users\n" "library_dir: /Library\n" "system_dir: /System\n" "macports_dir: /opt/local\n" "\n" "[Frameworks]\n" "Python: 3.2\n" "path: ${Common:system_dir}/Library/Frameworks/\n" "\n" "[Arthur]\n" "nickname: Two Sheds\n" "last_name: Jackson\n" "my_dir: ${Common:home_dir}/twosheds\n" "my_pictures: ${my_dir}/Pictures\n" "python_dir: ${Frameworks:path}/Python/Versions/${Frameworks:Python}" msgstr "" msgid "Mapping Protocol Access" msgstr "" 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 "" 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 "" 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 "" 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 "" msgid "" "\"a\" in parser[\"section\"]\n" "\"A\" in parser[\"section\"]" msgstr "" 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 "" msgid "``DEFAULTSECT`` cannot be removed from the parser:" msgstr "" msgid "trying to delete it raises :exc:`ValueError`," msgstr "" msgid "``parser.clear()`` leaves it intact," msgstr "" msgid "``parser.popitem()`` never returns it." msgstr "" 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 "" 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 "" 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 "" msgid "Customizing Parser Behaviour" msgstr "" 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 "" msgid "" "The most common way to change the way a specific config parser works is to " "use the :meth:`!__init__` options:" msgstr "" msgid "*defaults*, default value: ``None``" msgstr "" 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 "" msgid "" "Hint: if you want to specify default values for a specific section, " "use :meth:`~ConfigParser.read_dict` before you read the actual file." msgstr "" msgid "*dict_type*, default value: :class:`dict`" msgstr "" 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 "" msgid "" "An alternative dictionary type can be used for example to sort sections and " "options on write-back." msgstr "" 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 "" msgid "" ">>> parser = configparser.ConfigParser()\n" ">>> parser.read_dict({'section1': {'key1': 'value1',\n" "... 'key2': 'value2',\n" "... 'key3': 'value3'},\n" "... 'section2': {'keyA': 'valueA',\n" "... 'keyB': 'valueB',\n" "... 'keyC': 'valueC'},\n" "... 'section3': {'foo': 'x',\n" "... 'bar': 'y',\n" "... 'baz': 'z'}\n" "... })\n" ">>> parser.sections()\n" "['section1', 'section2', 'section3']\n" ">>> [option for option in parser['section3']]\n" "['foo', 'bar', 'baz']" msgstr "" msgid "*allow_no_value*, default value: ``False``" msgstr "" 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 "" msgid "" ">>> import configparser\n" "\n" ">>> sample_config = \"\"\"\n" "... [mysqld]\n" "... user = mysql\n" "... pid-file = /var/run/mysqld/mysqld.pid\n" "... skip-external-locking\n" "... old_passwords = 1\n" "... skip-bdb\n" "... # we don't need ACID today\n" "... skip-innodb\n" "... \"\"\"\n" ">>> config = configparser.ConfigParser(allow_no_value=True)\n" ">>> config.read_string(sample_config)\n" "\n" ">>> # Settings with values are treated as before:\n" ">>> config[\"mysqld\"][\"user\"]\n" "'mysql'\n" "\n" ">>> # Settings without values provide None:\n" ">>> config[\"mysqld\"][\"skip-bdb\"]\n" "\n" ">>> # Settings which aren't specified still raise an error:\n" ">>> config[\"mysqld\"][\"does-not-exist\"]\n" "Traceback (most recent call last):\n" " ...\n" "KeyError: 'does-not-exist'" msgstr "" msgid "*delimiters*, default value: ``('=', ':')``" msgstr "" 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 "" msgid "" "See also the *space_around_delimiters* argument " "to :meth:`ConfigParser.write`." msgstr "" msgid "*comment_prefixes*, default value: ``('#', ';')``" msgstr "" msgid "*inline_comment_prefixes*, default value: ``None``" msgstr "" 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 "" msgid "" "In previous versions of :mod:`!configparser` behaviour matched " "``comment_prefixes=('#',';')`` and ``inline_comment_prefixes=(';',)``." msgstr "" 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 "" msgid "" ">>> from configparser import ConfigParser, ExtendedInterpolation\n" ">>> parser = ConfigParser(interpolation=ExtendedInterpolation())\n" ">>> # the default BasicInterpolation could be used as well\n" ">>> parser.read_string(\"\"\"\n" "... [DEFAULT]\n" "... hash = #\n" "...\n" "... [hashes]\n" "... shebang =\n" "... ${hash}!/usr/bin/env python\n" "... ${hash} -*- coding: utf-8 -*-\n" "...\n" "... extensions =\n" "... enabled_extension\n" "... another_extension\n" "... #disabled_by_comment\n" "... yet_another_extension\n" "...\n" "... interpolation not necessary = if # is not at line start\n" "... even in multiline values = line #1\n" "... line #2\n" "... line #3\n" "... \"\"\")\n" ">>> print(parser['hashes']['shebang'])\n" "\n" "#!/usr/bin/env python\n" "# -*- coding: utf-8 -*-\n" ">>> print(parser['hashes']['extensions'])\n" "\n" "enabled_extension\n" "another_extension\n" "yet_another_extension\n" ">>> print(parser['hashes']['interpolation not necessary'])\n" "if # is not at line start\n" ">>> print(parser['hashes']['even in multiline values'])\n" "line #1\n" "line #2\n" "line #3" msgstr "" msgid "*strict*, default value: ``True``" msgstr "" msgid "" "When set to ``True``, the parser will not allow for any section or option " "duplicates while reading from a single source " "(using :meth:`~ConfigParser.read_file`, :meth:`~ConfigParser.read_string` " "or :meth:`~ConfigParser.read_dict`). It is recommended to use strict " "parsers in new applications." msgstr "" msgid "" "In previous versions of :mod:`!configparser` behaviour matched " "``strict=False``." msgstr "" msgid "*empty_lines_in_values*, default value: ``True``" msgstr "" 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 "" msgid "" "[Section]\n" "key = multiline\n" " value with a gotcha\n" "\n" " this = is still a part of the multiline value of 'key'" msgstr "" 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 "" msgid "" "*default_section*, default value: ``configparser.DEFAULTSECT`` (that is: " "``\"DEFAULT\"``)" msgstr "" 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 "" msgid "*interpolation*, default value: ``configparser.BasicInterpolation``" msgstr "" 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 "" msgid "*converters*, default value: not set" msgstr "" 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 "" 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 "" 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 "" 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 "" msgid "" ">>> custom = configparser.ConfigParser()\n" ">>> custom['section1'] = {'funky': 'nope'}\n" ">>> custom['section1'].getboolean('funky')\n" "Traceback (most recent call last):\n" "...\n" "ValueError: Not a boolean: nope\n" ">>> custom.BOOLEAN_STATES = {'sure': True, 'nope': False}\n" ">>> custom['section1'].getboolean('funky')\n" "False" msgstr "" msgid "" "Other typical Boolean pairs include ``accept``/``reject`` or ``enabled``/" "``disabled``." msgstr "" 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 "" msgid "" ">>> config = \"\"\"\n" "... [Section1]\n" "... Key = Value\n" "...\n" "... [Section2]\n" "... AnotherKey = Value\n" "... \"\"\"\n" ">>> typical = configparser.ConfigParser()\n" ">>> typical.read_string(config)\n" ">>> list(typical['Section1'].keys())\n" "['key']\n" ">>> list(typical['Section2'].keys())\n" "['anotherkey']\n" ">>> custom = configparser.RawConfigParser()\n" ">>> custom.optionxform = lambda option: option\n" ">>> custom.read_string(config)\n" ">>> list(custom['Section1'].keys())\n" "['Key']\n" ">>> list(custom['Section2'].keys())\n" "['AnotherKey']" msgstr "" 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 "" 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 "" msgid "" ">>> import re\n" ">>> config = \"\"\"\n" "... [Section 1]\n" "... option = value\n" "...\n" "... [ Section 2 ]\n" "... another = val\n" "... \"\"\"\n" ">>> typical = configparser.ConfigParser()\n" ">>> typical.read_string(config)\n" ">>> typical.sections()\n" "['Section 1', ' Section 2 ']\n" ">>> custom = configparser.ConfigParser()\n" ">>> custom.SECTCRE = re.compile(r\"\\[ *(?P<header>[^]]+?) *\\]\")\n" ">>> custom.read_string(config)\n" ">>> custom.sections()\n" "['Section 1', 'Section 2']" msgstr "" 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 "" msgid "Legacy API Examples" msgstr "" 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 "" msgid "An example of writing to a configuration file::" msgstr "" msgid "" "import configparser\n" "\n" "config = configparser.RawConfigParser()\n" "\n" "# Please note that using RawConfigParser's set functions, you can assign\n" "# non-string values to keys internally, but will receive an error when\n" "# attempting to write to a file or when you get it in non-raw mode. Setting\n" "# values using the mapping protocol or ConfigParser's set() does not allow\n" "# such assignments to take place.\n" "config.add_section('Section1')\n" "config.set('Section1', 'an_int', '15')\n" "config.set('Section1', 'a_bool', 'true')\n" "config.set('Section1', 'a_float', '3.1415')\n" "config.set('Section1', 'baz', 'fun')\n" "config.set('Section1', 'bar', 'Python')\n" |
| You are visitor 01402520 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |