Message174196
> It's possible to distribute Python packages with non-ASCII filenames.
Well, it wasn't until very recently (distribute 0.6.29):
https://bitbucket.org/tarek/distribute/issue/303/no-support-for-unicode-manifest-files
Unless we are not talking about the same thing, which is possible. ;-)
>> 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.
This was done on purpose, to test how Python fares. Such files can easily come into existence, e.g. when cloning a Git repo created on a different system. I am not after "correct" ZIP files in this case, I am after Python not raising UnicodeErrors when it is supposed to a) support non-ASCII module names and b) support surrogates.
python setup.py sdist --formats=gztar -> works
python setup.py sdist --formats=zip -> UnicodeError
If I am the only one to think this is wrong, then so be it. Our current workaround is to disallow surrogates in the manifest. /me shrugs. |
|
Date |
User |
Action |
Args |
2012-10-30 10:06:22 | stefanholek | set | recipients:
+ stefanholek, vstinner, ezio.melotti, Arfrever, r.david.murray, asvetlov, serhiy.storchaka |
2012-10-30 10:06:21 | stefanholek | set | messageid: <1351591581.98.0.957725964626.issue16310@psf.upfronthosting.co.za> |
2012-10-30 10:06:21 | stefanholek | link | issue16310 messages |
2012-10-30 10:06:21 | stefanholek | create | |
|