Message118263
| Author |
loewis |
| Recipients |
ixokai, lemburg, loewis, pitrou, pjenvey, ronaldoussoren, vstinner |
| Date |
2010年10月09日.10:47:46 |
| SpamBayes Score |
0.00014096472 |
| Marked as misclassified |
No |
| Message-id |
<4CB04850.4000200@v.loewis.de> |
| In-reply-to |
<1286617506.3177.7.camel@localhost.localdomain> |
| Content |
> The most likely values to be non-ASCII are, therefore, file paths. So it
> would make sense to also use the filesystem encoding for environment
> variables (so as to satisfy the common case).
-1. Environment variables are typically set in a text editor or on
the command line, so they will typically have the locale's encoding.
Applications that wish to support the case that fsencoding != locale
can recode the file names if desired, or use environb in the first
place.
If the mere existence of the fsname encoding leads to that much
confusion, I think I also support its removal. |
|