Antoine Pitrou <pit...@free.fr> added the comment: > Possibly of more interest for Python is that it's no longer buildable > without wchar_t support. While unicodeobject is pretty good at > checking HAVE_WCHAR_H, a number of modules and even pythonrun.c > directly use wchar_t or functions like PyUnicode_FromWideChar without > providing a fallback. Does Python 3 now require wchar_t or are these > bugs? (either option seems sensible).
It's pretty much required since we rely on mbstowcs and friends to convert some 8-bit strings (such as environment variables, command-line args...) to unicode. > At least in Android the distinction doesn't seem to matter as > Android's internationalziation/localization policy seems to be "use > Java". Ha :-) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12010> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
