➜

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 ishimoto, ubershmekel, vstinner
Date 2011-10-26.00:12:43
SpamBayes Score 0.00016812277
Marked as misclassified No
Message-id <4EA750BF.6010505@haypocalc.com>
In-reply-to <1319585530.67.0.809395329671.issue13247@psf.upfronthosting.co.za>
Content 
Le 26/10/2011 01:32, Atsuo Ishimoto a écrit :
> - I don't think filenames cannot be decoded in ANSI code page are rare enough to be ignored.

The issue is able being able to be noticied of encoding errors. 
Currently, unencodable characters are silently replaced and you don't 
know if the filename is valid or not. If a UnicodeEncodeError is raised, 
you will be noticed and so you have to fix the problem.

Anyway, you must use the Unicode API on Windows. If you use the Unicode 
API, filenames are no more encoded and code pages are no more used, so 
bye bye Unicode errors!

The Windows bytes API is just kept for backward compatibility. More 
details in my email to python-dev:
http://mail.python.org/pipermail/python-dev/2011-October/114203.html
History
Date User Action Args
2011-10-26 00:12:44vstinnersetrecipients: + vstinner, ishimoto, ubershmekel
2011-10-26 00:12:43vstinnerlinkissue13247 messages
2011-10-26 00:12:43vstinnercreate