Message131144
| Author |
aronacher |
| Recipients |
aronacher |
| Date |
2011年03月16日.17:26:33 |
| SpamBayes Score |
6.056202e-07 |
| Marked as misclassified |
No |
| Message-id |
<1300296395.6.0.964785890032.issue11574@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Right now Python happily falls back to ASCII if it can not parse your LC_CTYPE or something similar happens. Instead of falling back to ASCII it would be better if it falls back to UTF-8.
Alternatively it should at least give a warning that it's falling back to ASCII.
This issue was discussed at PyCon and the consensus so far was that falling back to UTF-8 in 3.3 might be a good idea and should not break much code as UTF-8 is a superset of ASCII. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年03月16日 17:26:35 | aronacher | set | recipients:
+ aronacher |
| 2011年03月16日 17:26:35 | aronacher | set | messageid: <1300296395.6.0.964785890032.issue11574@psf.upfronthosting.co.za> |
| 2011年03月16日 17:26:33 | aronacher | link | issue11574 messages |
| 2011年03月16日 17:26:33 | aronacher | create |
|