FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

bpo-45217: adds note that `allow_no_value` in `configparser` is optio… · python/cpython@3ea1c4b · GitHub

/ cpython Public

Commit 3ea1c4b

Browse files
bpo-45217: adds note that allow_no_value in configparser is optional (GH-28396) (GH-28416)
Co-authored-by: Łukasz Langa <lukasz@langa.pl> (cherry picked from commit cb07838) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
1 parent 9f64b1a commit 3ea1c4b

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

‎Doc/library/configparser.rst‎

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

0 commit comments

Comments
 (0)

Back | FazBrowse Home | New Git URL