From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Fri, 17 Sep 2021 11:41:25 +0000 (-0700) Subject: bpo-45217: adds note that `allow_no_value` in `configparser` is optional (GH-28396... X-Git-Tag: v3.9.8~157 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=3ea1c4b66887e7ca920db487f6ffc5f1db3c873f;p=thirdparty%2FPython%2Fcpython.git bpo-45217: adds note that `allow_no_value` in `configparser` is optional (GH-28396) (GH-28416) Co-authored-by: Łukasz Langa (cherry picked from commit cb07838ab756564988b1ffd23871f1222a832446) Co-authored-by: Nikita Sobolev --- diff --git a/Doc/library/configparser.rst b/Doc/library/configparser.rst index 3de5918367ac..60d33f59276f 100644 --- a/Doc/library/configparser.rst +++ b/Doc/library/configparser.rst @@ -237,7 +237,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.