Message118492
| Author |
vstinner |
| Recipients |
eric.araujo, r.david.murray, vstinner |
| Date |
2010年10月13日.00:25:37 |
| SpamBayes Score |
8.1944845e-06 |
| Marked as misclassified |
No |
| Message-id |
<1286929549.16.0.521717656075.issue10039@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> Is it always correct to decode a filename with the locale encoding
> on Unix?
Do you know something better than the locale encoding? I don't.
> Can’t each filesystem have its own encoding?
Yes, but how do you get the encoding of each filesystem? I think that few or no application support such case without mojibake. Backup programs can use the "raw" (bytes) API of Python 3 to avoid all encoding issues.
--
As wrote R. David Murray, read issue #9992 if you would like to know more about this problem and the different proposed solutions. I voted for removal of PYTHONFSENCODING which fix most issues. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年10月13日 00:25:49 | vstinner | set | recipients:
+ vstinner, eric.araujo, r.david.murray |
| 2010年10月13日 00:25:49 | vstinner | set | messageid: <1286929549.16.0.521717656075.issue10039@psf.upfronthosting.co.za> |
| 2010年10月13日 00:25:38 | vstinner | link | issue10039 messages |
| 2010年10月13日 00:25:37 | vstinner | create |
|