Message114358
| Author |
vstinner |
| Recipients |
Arfrever, lemburg, pitrou, vstinner |
| Date |
2010年08月19日.12:49:46 |
| SpamBayes Score |
1.2709357e-06 |
| Marked as misclassified |
No |
| Message-id |
<201008191449.39531.victor.stinner@haypocalc.com> |
| In-reply-to |
<4C6D2203.2070305@egenix.com> |
| Content |
> > Oh, I realized that PYTHONFSENCODING is ignored on Windows and Mac OS X.
> > r84201 and r84202 fix test_sys, and r84203 fixes the documentation and
> > Python usage (hide PYTHONFSENCODING variable in Python help on Windows
> > and Mac OS X).
>
> This has to be changed: The env var needs to be respected on all
> platforms.
I don't think so.
On Mac OS X, you cannot create a file with an invalid utf-8 name. The VFS uses
utf-8:
http://developer.apple.com/mac/library/qa/qa2001/qa1173.html
Use a different encoding will raise error for the first non-ascii filename.
--
About Windows, Python3 uses the wide character API of Windows, except in some
functions using third party libraries only providing a bytes API (eg.
openssl). filenames are stored as unicode, even on removable media like CD-Rom
or USB keys. I don't get the usecase here. Why would you like to change the
filesystem encoding on Windows? |
|