➜

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 vstinner
Recipients Arfrever, asvetlov, ezio.melotti, r.david.murray, serhiy.storchaka, stefanholek, vstinner
Date 2012-10-30.00:37:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1351557451.24.0.701823412729.issue16310@psf.upfronthosting.co.za>
In-reply-to
Content 
> The use-case is building Python distributions containing
> non-ASCII filenames.

It's possible to distribute Python packages with non-ASCII filenames.

> So yes, I have Latin-1 bytes on the filesystem,
> even though my locale is UTF-8.

You system is not configured correctly. If you would like to distribute such invalid filename, how do you plan to access it on other platforms where the filename is decoded differently? It would be safer to build your project on a well configured system.

See issues mentionned in msg173766 to support: creating a ZIP archive with invalid filenames, and be able to specify the encoding of filenames when decoding a ZIP archive.
History
Date User Action Args
2012-10-30 00:37:31vstinnersetrecipients: + vstinner, ezio.melotti, Arfrever, r.david.murray, asvetlov, stefanholek, serhiy.storchaka
2012-10-30 00:37:31vstinnersetmessageid: <1351557451.24.0.701823412729.issue16310@psf.upfronthosting.co.za>
2012-10-30 00:37:31vstinnerlinkissue16310 messages
2012-10-30 00:37:30vstinnercreate