Message205505
| Author |
ncoghlan |
| Recipients |
deleted250130, larry, lemburg, loewis, ncoghlan, pitrou, r.david.murray, terry.reedy, vstinner |
| Date |
2013年12月08日.02:16:02 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1386468963.76.0.589393750893.issue19846@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Note that the *only* change Antoine's patch makes is that:
- *if* the locale encoding is ASCII (or an alias for ASCII)
- *then* Python sets the filesystem encoding to UTF-8 instead
If the locale encoding is anything *other* than ASCII, then that will still be used as the filesystem encoding, so environments that use something other than ASCII for the C locale will retain their current behaviour.
The rationale for this approach is based on the assumption that the *most likely* way to get a locale encoding of ASCII at this point in time is to use "LANG=C" on a system where the locale encoding is normally something more suited to a Unicode world (likely UTF-8).
Will assuming utf-8 sometimes cause problems? Quite possibly. But assuming that the platform's claim to only support ASCII is correct causes serious usability problems, too. |
|