➜

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 amaury.forgeotdarc, georg.brandl, ronaldoussoren, vstinner
Date 2011-01-21.11:08:22
SpamBayes Score 6.0411254e-05
Marked as misclassified No
Message-id <1295608104.48.0.695311537372.issue10955@psf.upfronthosting.co.za>
In-reply-to
Content 
Ronald Oussoren and Amaury Forgeot d'Arc: do you think that it is an acceptable limitation to only accept ASCII filenames in python32.zip? (not in all ZIP files, just in the file loaded at startup)

All possible solutions:

 a) Only accept ASCII filenames in python32.zip
 b) Only accept ZIP archive using UTF-8 filenames (unicode flag set for all files in the archive). On Linux, I don't know how to create such archive. I suppose that most ZIP archivers prefer the legacy format (unicode flag unset). But few people produce python32.zip files, maybe only py2exe / pyfreeze developers.
 c) Add encodings/cp437.py to your python3.2/ directory (outside the ZIP file), which can be a problem :-/
 d) Implement cp437 in C

I dislike (c) and (d), but I cannot say if (a) or (b) is better.
History
Date User Action Args
2011-01-21 11:08:24vstinnersetrecipients: + vstinner, georg.brandl, ronaldoussoren, amaury.forgeotdarc
2011-01-21 11:08:24vstinnersetmessageid: <1295608104.48.0.695311537372.issue10955@psf.upfronthosting.co.za>
2011-01-21 11:08:22vstinnerlinkissue10955 messages
2011-01-21 11:08:22vstinnercreate