Message132831
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? |
|
Date |
User |
Action |
Args |
2011-04-03 03:32:38 | Daniel.Goertzen | set | recipients:
+ Daniel.Goertzen, amaury.forgeotdarc, atuining, belopolsky, pitrou, vstinner, grahamd, flox |
2011-04-03 03:32:38 | Daniel.Goertzen | set | messageid: <1301801558.69.0.0992943614849.issue6501@psf.upfronthosting.co.za> |
2011-04-03 03:32:38 | Daniel.Goertzen | link | issue6501 messages |
2011-04-03 03:32:37 | Daniel.Goertzen | create | |
|