Rewrite plistlib with functional style
Open
Nobody has claimed this yet.
3.13
performance
stdlib
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 32196 |
|---|---|
| Nosy | @ronaldoussoren, @serhiy-storchaka |
| 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 = None
created_at = <Date 2017-12-01.19:28:36.864>
labels = ['3.7', 'library', 'performance']
title = 'Rewrite plistlib with functional style'
updated_at = <Date 2017-12-26.10:47:13.731>
user = 'https://github.com/serhiy-storchaka'
bugs.python.org fields:
activity = <Date 2017-12-26.10:47:13.731>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-12-01.19:28:36.864>
creator = 'serhiy.storchaka'
dependencies = []
files = []
hgrepos = []
issue_num = 32196
keywords = ['patch']
message_count = 3.0
messages = ['307404', '307508', '309058']
nosy_count = 2.0
nosy_names = ['ronaldoussoren', 'serhiy.storchaka']
pr_nums = ['4671']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'performance'
url = 'https://bugs.python.org/issue32196'
versions = ['Python 3.7']
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 names plistlib and references python/cpython#4671, but gives no file, test, or acceptance criteria. Start by reading the referenced PR and locating plistlib in the CPython library; completion criteria need to be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100