zipfile extractall needlessly re-wraps ZipInfo instances
Open
Nobody has claimed this yet.
3.8 (EOL)
pending
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 32742 |
|---|---|
| Nosy | @serhiy-storchaka, @peterbe |
| 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 2018-02-01.15:10:53.067>
labels = ['3.8', 'type-feature', 'library']
title = 'zipfile extractall needlessly re-wraps ZipInfo instances'
updated_at = <Date 2018-03-27.16:53:40.745>
user = 'https://github.com/peterbe'
bugs.python.org fields:
activity = <Date 2018-03-27.16:53:40.745>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-02-01.15:10:53.067>
creator = 'peterbe'
dependencies = []
files = []
hgrepos = []
issue_num = 32742
keywords = ['patch']
message_count = 3.0
messages = ['311434', '311435', '314539']
nosy_count = 2.0
nosy_names = ['serhiy.storchaka', 'peterbe']
pr_nums = ['5472']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue32742'
versions = ['Python 3.8']
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 at the zipfile extractall entry point and review the context of PR 5472, which is named in the issue metadata. Confirm how ZipInfo instances are currently re-wrapped; done means extractall no longer performs that unnecessary re-wrapping while preserving its existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100