Feature: provide (safe) traversal/extraction facilities for `zipfile.Path`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
zipfile.Path could provide its own traversal that could offer some safety checks.
Something like that might be nice. Though perhaps it could be more generic instead of being part of zipfile.Path, even if zipfile.Path would then perhaps provide an extraction API using that?
Originally posted by @obfusk in https://github.com/python/cpython/issues/123270#issuecomment-2330381740
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 identifies zipfile.Path as the entry point but does not name a source file, test, or concrete API design. First clarify whether traversal, extraction, or a generic facility is wanted, then define the safety checks and tests that would demonstrate the completed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100