Configparser is not reading Indended Sections as Mentioned in Docs
Open
Nobody has claimed this yet.
docs
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 41379 |
|---|---|
| PRs |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = <Date 2020-07-24.07:03:35.465>
created_at = <Date 2020-07-24.06:01:23.336>
labels = ['3.8', 'type-bug', 'library', 'invalid']
title = 'Configparser is not reading Indended Sections as Mentioned in Docs'
updated_at = <Date 2021-08-19.11:41:53.906>
user = 'https://bugs.python.org/VigneshRajendran'
bugs.python.org fields:
activity = <Date 2021-08-19.11:41:53.906>
actor = 'python-dev'
assignee = 'none'
closed = True
closed_date = <Date 2020-07-24.07:03:35.465>
closer = 'SilentGhost'
components = ['Library (Lib)']
creation = <Date 2020-07-24.06:01:23.336>
creator = 'Vignesh Rajendran'
dependencies = []
files = []
hgrepos = []
issue_num = 41379
keywords = []
message_count = 2.0
messages = ['374160', '374162']
nosy_count = 3.0
nosy_names = ['SilentGhost', 'python-dev', 'Vignesh Rajendran']
pr_nums = ['27830']
priority = 'normal'
resolution = 'not a bug'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41379'
versions = ['Python 3.8']
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
The migrated report points to bugs.python.org issue 41379 and PR #27830; start by reviewing those records and the ConfigParser documentation behavior described there. The issue was closed as “not a bug,” with no files or tests listed, so confirm whether any current discrepancy remains before proposing work.
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
- Needs clarification
- Newbie friendliness
- 10/100