zipfile library will raise uncaught oserror when reading length incorrect zip file
Open
Nobody has claimed this yet.
3.10
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 46931 |
|---|---|
| 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 2022-03-05.17:37:33.918>
labels = ['type-bug', 'library', '3.10']
title = 'zipfile library will raise uncaught oserror when reading length incorrect zip file'
updated_at = <Date 2022-03-05.17:37:33.918>
user = 'https://bugs.python.org/ultimalium'
bugs.python.org fields:
activity = <Date 2022-03-05.17:37:33.918>
actor = 'ultimalium'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2022-03-05.17:37:33.918>
creator = 'ultimalium'
dependencies = []
files = ['50658']
hgrepos = []
issue_num = 46931
keywords = []
message_count = 1.0
messages = ['414590']
nosy_count = 1.0
nosy_names = ['ultimalium']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue46931'
versions = ['Python 3.10']
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 reproducing the failure with damaged.zip using Python's zipfile library and inspect where reading the malformed archive raises the uncaught OSError. Done means the damaged archive is handled without an uncaught OSError, with the expected failure behavior confirmed by a regression check.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100