From: vidhya <96202776+Vidhyavinu@users.noreply.github.com>
Date: Tue, 22 Feb 2022 18:06:41 +0000 (-0500)
Subject: bpo-20923 : [doc] Explain ConfigParser 'valid section name'  and .SECTCRE (GH-31413)
X-Git-Tag: v3.11.0a6~131
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=bba8008f99d615a02984422a3825082bb5621f5a;p=thirdparty%2FPython%2Fcpython.git

bpo-20923 : [doc] Explain ConfigParser 'valid section name'  and .SECTCRE (GH-31413)
---

diff --git a/Doc/library/configparser.rst b/Doc/library/configparser.rst
index 1ebda53ecda0..323dd2affc78 100644
--- a/Doc/library/configparser.rst
+++ b/Doc/library/configparser.rst
@@ -267,6 +267,9 @@ 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.
 
+By default,  a valid section name can be any string that does not contain '\\n' or ']'.
+To change this, see :attr:`ConfigParser.SECTCRE`.
+
 Configuration files may include comments, prefixed by specific
 characters (``#`` and ``;`` by default [1]_).  Comments may appear on
 their own on an otherwise empty line, possibly indented. [1]_