[3.10] bpo-20923 : [doc] Explain ConfigParser 'valid section name' and .SECTCRE...

(cherry picked from commit bba8008f99d615a02984422a3825082bb5621f5a)

Co-authored-by: vidhya <96202776+Vidhyavinu@users.noreply.github.com>
Automerge-Triggered-By: GH:iritkatriel

diff --git a/Doc/library/configparser.rst b/Doc/library/configparser.rst
index 1ebda53ecda0fb9a9b0ec0bf4d9bc7b01574a0ba..323dd2affc78fc9a987d2927a125e7b07db9816c 100644 (file)
--- 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]_