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 sjt
Recipients gregory.p.smith, methane, ned.deily, serhiy.storchaka, sjt
Date 2022-03-23.14:02:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1648044126.15.0.155895523231.issue28080@roundup.psfhosted.org>
In-reply-to
Content
I'm not going to have time to look at the PR for a couple days.

I don't understand what the use case is for writing or appending with filenames in a non-UTF-8 encoding.  At least in my experience, reading such files is rare, but I have never been asked to write one.  The correspondents who send me zipfiles with the directory encoded in shift_jisx0213 are perfectly happy to read zipfiles with the directory encoded in UTF-8.

If that is true for other users, then unzipping the file to a temporary directory with the appropriate --metadata-encoding, adding the required paths there, and zipping a new archive seems perfectly workable.  In that case making this feature read-only makes the most sense to me.
History
Date User Action Args
2022-03-23 14:02:06sjtsetrecipients: + sjt, gregory.p.smith, ned.deily, methane, serhiy.storchaka
2022-03-23 14:02:06sjtsetmessageid: <1648044126.15.0.155895523231.issue28080@roundup.psfhosted.org>
2022-03-23 14:02:06sjtlinkissue28080 messages
2022-03-23 14:02:06sjtcreate