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 loewis
Date 2003-03-03.15:48:09
SpamBayes Score
Marked as misclassified
Logged In: YES 

I see. The right thing, IMO, is to always return Unicode
objects for Unicode arguments, just the same way the "et"
parser works: if the file system encoding is NULL, fall back
to the system default encoding. Then, you can generalize the
docs to [NT and Unix] (with OS X being a flavour of Unix),
or drop the OS reference completely (in which case the other
os modules are effectively buggy).

There might be a function already to fall back to the system
default encoding; perhaps just passing NULL works.

There should be a documentation section on Unicode file
names; I volunteer to write it (Summary: NT+ uses Unicode
natively, W9x uses "mbcs", OS X uses UTF-8, which equates to
"Unicode natively", Unices with nl_langinfo(CODEPAGE) use
that, all others use the system default encoding).
Date User Action Args
2007-08-23 15:20:30adminlinkissue683592 messages
2007-08-23 15:20:30admincreate