Marc-Andre Lemburg added the comment: The two functions serve a different purpose.
getdefautltlocale() specifically avoids calling setlocale() and is thread-safe on Unix. It's purpose is to return the default locale string, not only the encoding. getpreferredencoding() only returns the encoding, but on Unix has to call setlocale() to return correct results and thus is not thread-safe. Martin's comment doesn't address this difference and I don't agree with it. Regarding the different results, I guess this could be solved by having both function pass the data obtained from the system through _parse_localname() before returning it, but that would have to be a handled in a new issue report. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13074> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
