[Python-Dev] Python-3.0, unicode, and os.environ (original) (raw)
Lennart Regebro regebro at gmail.com
Fri Dec 12 19:21:31 CET 2008
- Previous message: [Python-Dev] Python-3.0, unicode, and os.environ
- Next message: [Python-Dev] Python-3.0, unicode, and os.environ
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Dec 12, 2008 at 16:21, Scott Dial <scott+python-dev at scottdial.com> wrote:
See the following email for a summary of existing practice (as of 2004):
http://www.mail-archive.com/unicode@unicode.org/msg27352.html
Interesting. Quite a lot of them do just drop the undecodable filenames. The Java solution with replacing it seems to be a better idea at first glance, but what if you then end up with two filenames that are the same? Possibly replacing with the <?> character is a good idea to notify that the file is there, but fail then fail to open it.
-- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64
- Previous message: [Python-Dev] Python-3.0, unicode, and os.environ
- Next message: [Python-Dev] Python-3.0, unicode, and os.environ
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]