GzipFile doesn't properly handle short reads and writes on the underlying stream
Open
Nobody has claimed this yet.
3.7 (EOL)
docs
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 28436 |
|---|---|
| Nosy | @socketpair, @vadmium |
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-10-13.20:29:24.336>
labels = ['type-bug', '3.7', 'docs']
title = "GzipFile doesn't properly handle short reads and writes on the underlying stream"
updated_at = <Date 2016-10-14.21:34:58.164>
user = 'https://bugs.python.org/abacabadabacaba'
bugs.python.org fields:
activity = <Date 2016-10-14.21:34:58.164>
actor = 'martin.panter'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2016-10-13.20:29:24.336>
creator = 'abacabadabacaba'
dependencies = []
files = []
hgrepos = []
issue_num = 28436
keywords = []
message_count = 4.0
messages = ['278606', '278609', '278610', '278667']
nosy_count = 4.0
nosy_names = ['abacabadabacaba', 'docs@python', 'socketpair', 'martin.panter']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue28436'
versions = ['Python 3.5', 'Python 3.6', '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
Start by locating the Python GzipFile implementation and its tests. Reproduce short reads and writes from an underlying stream, then determine the expected behavior and add coverage showing that the issue is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100