zipfile should catch ValueError as well as OSError to detect bad seek calls
Open
Nobody has claimed this yet.
3.11
stdlib
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 29468 |
|---|---|
| Nosy | @llllllllll, @FFY00, @iritkatriel |
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-02-07.03:14:05.339>
labels = ['library', '3.11']
title = 'zipfile should catch ValueError as well as OSError to detect bad seek calls'
updated_at = <Date 2021-05-24.18:42:06.427>
user = 'https://github.com/llllllllll'
bugs.python.org fields:
activity = <Date 2021-05-24.18:42:06.427>
actor = 'FFY00'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-02-07.03:14:05.339>
creator = 'llllllllll'
dependencies = []
files = []
hgrepos = []
issue_num = 29468
keywords = []
message_count = 3.0
messages = ['287185', '393314', '394263']
nosy_count = 3.0
nosy_names = ['llllllllll', 'FFY00', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue29468'
versions = ['Python 3.11']
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 concerns Python's zipfile library and its handling of bad seek calls. Start by locating the relevant error-handling entry point and any associated tests; confirm the expected behavior for both OSError and ValueError, then run the focused zipfile tests to verify that both cases are detected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100