Let ConfigParser parse systemd units
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 31528 |
|---|---|
| Nosy | @mcepl, @ambv, @cooperlees, @bbayles, @johnlinp |
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 2017-09-20.08:40:09.170>
labels = ['3.8', 'type-feature', 'library']
title = 'Let ConfigParser parse systemd units'
updated_at = <Date 2021-09-02.23:45:07.318>
user = 'https://github.com/johnlinp'
bugs.python.org fields:
activity = <Date 2021-09-02.23:45:07.318>
actor = 'cooperlees'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-09-20.08:40:09.170>
creator = 'johnlinp'
dependencies = []
files = []
hgrepos = []
issue_num = 31528
keywords = []
message_count = 1.0
messages = ['302604']
nosy_count = 5.0
nosy_names = ['mcepl', 'lukasz.langa', 'cooperlees', 'bbayles', 'johnlinp']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue31528'
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
Start by locating Python's ConfigParser implementation and its existing tests, then compare the requested systemd-unit support with the formats currently accepted. Define the parsing behavior and add coverage for representative units; done means ConfigParser accepts the requested units without regressing existing formats.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100