Fix base64-codec and bz2-codec incremental decoders
Open
Nobody has claimed this yet.
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 27799 |
|---|---|
| Nosy | @vadmium |
| Files |
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 2016-08-19.11:52:00.605>
labels = ['type-bug', 'library']
title = 'Fix base64-codec and bz2-codec incremental decoders'
updated_at = <Date 2016-08-19.11:52:00.605>
user = 'https://github.com/vadmium'
bugs.python.org fields:
activity = <Date 2016-08-19.11:52:00.605>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2016-08-19.11:52:00.605>
creator = 'martin.panter'
dependencies = []
files = ['44149']
hgrepos = []
issue_num = 27799
keywords = ['patch']
message_count = 1.0
messages = ['273106']
nosy_count = 1.0
nosy_names = ['martin.panter']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue27799'
versions = ['Python 2.7', 'Python 3.5', '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
Start by reading the mentioned base64-decoder.patch and locating the incremental-decoder entry points for the base64 and bz2 codecs. Use the patch to determine the intended behavior, then verify that both decoders meet it and that the relevant tests pass.
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
- 35/100