Skip to content

Commit c4e9ef1

Browse files
miss-islingtonsobolevn
authored andcommitted
bpo-45217: adds note that allow_no_value in configparser is optional (GH-28396) (GH-28418)
Co-authored-by: Łukasz Langa <[email protected]> (cherry picked from commit cb07838) Co-authored-by: Nikita Sobolev <[email protected]>
1 parent 81c9aff commit c4e9ef1

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

Doc/library/configparser.rst

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -261,7 +261,8 @@ A configuration file consists of sections, each led by a ``[section]`` header,
261261
followed by key/value entries separated by a specific string (``=`` or ``:`` by
262262
default [1]_). By default, section names are case sensitive but keys are not
263263
[1]_. Leading and trailing whitespace is removed from keys and values.
264-
Values can be omitted, in which case the key/value delimiter may also be left
264+
Values can be omitted if the parser is configured to allow it [1]_,
265+
in which case the key/value delimiter may also be left
265266
out. Values can also span multiple lines, as long as they are indented deeper
266267
than the first line of the value. Depending on the parser's mode, blank lines
267268
may be treated as parts of multiline values or ignored.

0 commit comments

Comments
 (0)