Message90308
> One *could* add a check in pythonrun.c to substitute some suitable
> default (UTF-8) if nl_langinfo(CODESET) returns an empty value.
While googling for the source of this problem, I found other software
projects that take this approach. It doesn't seem totally unreasonable.
I just wish I understood *why* nl_langinfo(CODESET) is returning "" in
these cases. I've looked for the source at
http://www.opensource.apple.com, but can't find it; maybe that part of
Darwin isn't open source.
It seems that a lot of people end up with an OS X Terminal setup such that
LC_CTYPE is 'UTF-8' (perhaps this is a 10.4 thing---I haven't encountered
this myself); I don't think these people should have to deal with a
confusing error on startup; defaulting to UTF-8 on OS X seems like a
reasonable compromise. |
|
Date |
User |
Action |
Args |
2009-07-09 07:51:48 | mark.dickinson | set | recipients:
+ mark.dickinson, ronaldoussoren, ned.deily, Phil |
2009-07-09 07:51:48 | mark.dickinson | set | messageid: <1247125908.54.0.575386464499.issue6393@psf.upfronthosting.co.za> |
2009-07-09 07:51:47 | mark.dickinson | link | issue6393 messages |
2009-07-09 07:51:46 | mark.dickinson | create | |
|