This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients 18z, christian.heimes, krnick, serhiy.storchaka, vstinner, xtreak
Date 2019-04-02.11:09:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1554203342.54.0.160280980509.issue36260@roundup.psfhosted.org>
In-reply-to
Content
I am against such trivial methods in ZipFile. Its interface is already complicate. The advantage of Python is that you do not need tons of methods for every possible query -- you can just combine few Python features into a one-line expression.

As for the documentation change, it could be useful to add more general note about possible pitfalls. What happen when interrupt extracting or adding to the archive, what happen when extract into existing tree or overwrite an existing file, what happen when the file system does not support some file names, what happen when extract to case-insensitive file system, what happen when extract encrypted file with wrong password, etc. We do not have to tell the user what he should not do, just to warn about the possible consequences.
History
Date User Action Args
2019-04-02 11:09:02serhiy.storchakasetrecipients: + serhiy.storchaka, vstinner, christian.heimes, 18z, xtreak, krnick
2019-04-02 11:09:02serhiy.storchakasetmessageid: <1554203342.54.0.160280980509.issue36260@roundup.psfhosted.org>
2019-04-02 11:09:02serhiy.storchakalinkissue36260 messages
2019-04-02 11:09:02serhiy.storchakacreate