configparser.write() does not save comments.
Open
Nobody has claimed this yet.
extension-modules
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 33481 |
|---|---|
| Nosy | @ambv, @vadmium, @pebaudhi |
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 = None
created_at = <Date 2018-05-13.10:26:00.104>
labels = ['extension-modules', 'type-bug']
title = 'configparser.write() does not save comments.'
updated_at = <Date 2018-05-14.09:43:38.555>
user = 'https://github.com/pebaudhi'
bugs.python.org fields:
activity = <Date 2018-05-14.09:43:38.555>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules']
creation = <Date 2018-05-13.10:26:00.104>
creator = 'pebaudhi'
dependencies = []
files = []
hgrepos = []
issue_num = 33481
keywords = []
message_count = 2.0
messages = ['316457', '316497']
nosy_count = 3.0
nosy_names = ['lukasz.langa', 'martin.panter', 'pebaudhi']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue33481'
versions = ['Python 3.6']
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 issue identifies configparser.write() as the affected entry point but names no file or test. Locate that implementation and determine how comments are represented before writing; done means written configuration files preserve comments, with coverage added in the relevant test area.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100