Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

bpo-45217: adds note that allow_no_value in configparser is optional #28396

Merged
merged 2 commits into from Sep 17, 2021
Merged

bpo-45217: adds note that allow_no_value in configparser is optional #28396

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7edbc25
bpo-45217: adds note that `allow_no_value` in `configparser` is optional
sobolevn Sep 16, 2021
7956d21
Be more specific about what "optionally" means
ambv Sep 17, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 2 additions & 1 deletion Doc/library/configparser.rst
View file
Open in desktop
Expand Up @@ -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.
Expand Down