Repository navigation
configparser: create unnamed section with mapping protocol access #136282
Description
Feature or enhancement
Current state (3.14):
Since gh-123077 (CPython 3.14), it is possible to create an unnamed section with configparser:
>>> cfg1 = configparser.ConfigParser(allow_unnamed_section=True)
>>> cfg1.add_section(configparser.UNNAMED_SECTION)
>>> cfg1.set(configparser.UNNAMED_SECTION, "foo", "bar")
>>> cfg1.write(fobj1)This gives the following output file:
foo = bar
However, the mapping protocol access is not supported:
>>> cfg2 = configparser.ConfigParser(allow_unnamed_section=True)
>>> cfg2[configparser.UNNAMED_SECTION] = {"foo": "bar"}
>>> cfg2.write(fobj2)Gives the following output file:
[<UNNAMED_SECTION>]
foo = bar
Proposal:
Implement the mapping protocol for access of the unnamed section in configparser.
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Links to previous discussion of this feature:
No response
Activity
pythongh-136282: configparser: create unnamed sections via mapping pr…
merwok commentedon Nov 27, 2025
I am not sure this should be a feature: I can’t see someone wanting the current behaviour.
merwok commentedon Nov 27, 2025
@ambv (for configparser) and @hugovk (RM), would you call this a feature or fix?
gh-136282: Configparser: create unnamed sections via mapping protocol…
pythongh-136282: Configparser: create unnamed sections via mapping pr…
pythongh-136282: Configparser: create unnamed sections via mapping pr…
[3.14] gh-136282: Configparser: create unnamed sections via mapping p…
encukou commentedon Jan 6, 2026
Thank you for the fix!