-
-
Notifications
You must be signed in to change notification settings - Fork 30.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: provide (safe) traversal/extraction facilities for zipfile.Path
#123727
Comments
zipfile.Path
zipfile.Path
As mentioned in that issue, there does already exist one extraction API in One thing to be careful about when extracting is that using Before we embark on any implementation, let's first capture what are the motivations, use-cases, and requirements for such a feature? Who would use it and how? |
For example, returning a list after calling, right? |
Perhaps. We're looking for more complete user stories. For example:
That's a contrived user story as an illustration. What I want are real user stories from users who have legitimate use-cases that aren't met by the current |
Being able to combine FYI: I just noticed |
Something like that might be nice. Though perhaps it could be more generic instead of being part of
zipfile.Path
, even ifzipfile.Path
would then perhaps provide an extraction API using that?Originally posted by @obfusk in #123270 (comment)
The text was updated successfully, but these errors were encountered: