Daniel Goertzen <daniel.goert...@gmail.com> added the comment: It turns out that cx-freeze deliberately sets Py_IgnoreEnvironmentFlag to ensure that the final executable is really an isolated, standalone executable (ie, it can't be subverted by setting PYTHONPATH.) Therefore the PYTHONIOENCODING work-around does not work in this situation.
I am currently using a cx-freeze work-around from the author to enable the PYTHONIOENCODING work-around. Altogether not that pleasant. Could Python 3 could just default to some reasonable encoding and keep on chugging? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6501> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
