configparser no longer accept space as a delimiter
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Bug report
Bug description:
Between python 3.14.4 and 3.14.5, python stopped recognising a space as a delimiter.
import configparser
cp=configparser.ConfigParser(delimiters=(' ', '='))
cp.read_string('[all]\nfoo bar=baz')
cp.options('all')
Test using docker on 3.14.4:
$ docker run -it --rm python:3.14.4
Python 3.14.4 (main, May 8 2026, 22:38:20) [GCC 14.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import configparser; cp=configparser.ConfigParser(delimiters=(' ', '=')); cp.read_string('[all]\nfoo bar=baz'); cp.options('all')
['foo']
Same test on 3.14.5:
$ docker run -it --rm python:3.14.5
Python 3.14.5 (main, May 20 2026, 02:52:14) [GCC 14.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import configparser; cp=configparser.ConfigParser(delimiters=(' ', '=')); cp.read_string('[all]\nfoo bar=baz'); cp.options('all')
['foo bar']
Between 3.13.13 and 3.13.14, the same issue appears.
I dug into Lib/configparser.py and its history a bit and I suspect this might be related to https://github.com/python/cpython/pull/146399, although I did not dig deep enough to be sure this test is valid and has the proper input:
Python 3.14.7 (main, Aug 5 2026, 10:29:49) [Clang 21.0.0 (clang-2100.1.1.101)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> delimiters = (' ', '=')
>>> d = "|".join(re.escape(d) for d in delimiters)
>>> _OPT_NV_TMPL_PRE = r"""
... (?P<option>.*?)
... \s*(?: # any number of space/tab,
... (?P<vi>{delim})\s* # optionally followed by
... # any of allowed
... # delimiters, followed by any
... # space/tab
... (?P<value>.*))?$ # everything up to eol
... """
>>> _OPT_NV_TMPL_POST = r"""
... (?P<option> # very permissive!
... (?:(?!{delim})\S)* # non-delimiter non-whitespace
... (?:\s+(?:(?!{delim})\S)+)*) # optionally more words
... \s*(?: # any number of space/tab,
... (?P<vi>{delim})\s* # optionally followed by
... # any of the allowed
... # delimiters, followed by any
... # space/tab
... (?P<value>.*))?$ # everything up to eol
... """
>>> _optcre_pre = re.compile(_OPT_NV_TMPL_PRE.format(delim=d), re.VERBOSE)
>>> _optcre_post = re.compile(_OPT_NV_TMPL_POST.format(delim=d), re.VERBOSE)
>>> _optcre_pre.search('foo bar').groups()
('foo', ' ', 'bar')
>>> _optcre_post.search('foo bar').groups()
('foo bar', None, None)
CPython versions tested on:
3.14
Operating systems tested on:
Linux
Linked PRs
- gh-156382
- gh-156557
- gh-156558
- gh-156559
- gh-156560
- gh-156561
- gh-156562
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in Lib/configparser.py and reproduce the delimiter behavior with the Python 3.13.13/3.13.14 or 3.14.4/3.14.5 examples from the report. Inspect the parser regex history, including PR 146399, and compare the linked PRs; done means space delimiters parse as previously documented and regression coverage verifies the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100