gzip module failing to decompress valid compressed file
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the gzip module issue and the existing python/cpython#29847 patch, then consult the original BPO issue 24301 for the missing reproduction details. Done means the gzip module successfully decompresses the valid compressed file described by the report, with the behavior covered by the relevant tests identified during review.
Written by the indexing model from the issue text.
Description
| BPO | 24301 |
|---|---|
| Nosy | @ned-deily, @vadmium, @iritkatriel, @rhpvorderman |
| 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 2015-05-27.15:59:03.363>
labels = ['type-bug', 'library', '3.9', '3.10', '3.11']
title = 'gzip module failing to decompress valid compressed file'
updated_at = <Date 2021-12-31.09:44:00.395>
user = 'https://bugs.python.org/Ericg'
bugs.python.org fields:
activity = <Date 2021-12-31.09:44:00.395>
actor = 'rhpvorderman'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-05-27.15:59:03.363>
creator = 'Ericg'
dependencies = []
files = []
hgrepos = []
issue_num = 24301
keywords = ['patch']
message_count = 9.0
messages = ['244188', '244214', '244230', '245368', '245369', '407148', '407280', '407282', '409410']
nosy_count = 6.0
nosy_names = ['ned.deily', 'martin.panter', 'Ericg', 'nczeczulin', 'iritkatriel', 'rhpvorderman']
pr_nums = ['29847']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue24301'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·
-
link-check link-check:sphinx-theme
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
modelscope/DiffSynth-Studio#1702 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
qgis/QGIS-Documentation#11275 ·
-
bug priority:normal ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
OpenHands/extensions#626 · 1 comment ·