From: Nikita Sobolev Date: Fri, 17 Sep 2021 10:55:51 +0000 (+0300) Subject: bpo-45217: adds note that `allow_no_value` in `configparser` is optional (GH-28396) X-Git-Tag: v3.11.0a1~144 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=cb07838ab756564988b1ffd23871f1222a832446;p=thirdparty%2FPython%2Fcpython.git bpo-45217: adds note that `allow_no_value` in `configparser` is optional (GH-28396) Co-authored-by: Łukasz Langa --- diff --git a/Doc/library/configparser.rst b/Doc/library/configparser.rst index 1ec0fa1586af..d31452edb974 100644 --- a/Doc/library/configparser.rst +++ b/Doc/library/configparser.rst @@ -261,7 +261,8 @@ 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 +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.