[issue6501] Fatal error on startup with invalid PYTHONIOENCODING

STINNER Victor added the comment: > Is there anything to backport as referred to in msg136670 or can this be > closed? The fix is present in Python 3.3 since Python 3.3.0 according to the changelog. Python 3.2 doesn't accept bugfixes anymore. Python 2.7 doesn't have the function os.device_enc

[issue6501] Fatal error on startup with invalid PYTHONIOENCODING

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue6501] Fatal error on startup with invalid PYTHONIOENCODING

Mark Lawrence added the comment: Is there anything to backport as referred to in msg136670 or can this be closed? -- nosy: +BreamoreBoy ___ Python tracker ___

[issue6501] Fatal error on startup with invalid PYTHONIOENCODING

Éric Araujo added the comment: > Currently different environment variables are treated differently. For > example, > mistakes in PYTHONHOME and PYTHONIOENCODING cause fatal error while an error > in > PYTHONSTARTUP is reported but does not terminate python: If PYTHONSTARTUP is the only envva

[issue6501] Fatal error on startup with invalid PYTHONIOENCODING

STINNER Victor added the comment: @grahamd: Can you try the development version of Python 3.3, or try to patch your version using device_encoding.patch? You will not get cp0 encoding anymore. If the patch fixes your issue, I will backport it. I don't see anything interesting to do for this is

[issue6501] Fatal error on startup with invalid PYTHONIOENCODING

Roundup Robot added the comment: New changeset 5783a55a2418 by Victor Stinner in branch 'default': Issue #6501: os.device_encoding() returns None on Windows if the application http://hg.python.org/cpython/rev/5783a55a2418 -- nosy: +python-dev ___ Pyt

[issue6501] Fatal error on startup with invalid PYTHONIOENCODING

STINNER Victor added the comment: > On a Western Windows, I suggest >PYTHONIOENCODING=cp1252:backslashreplace Why using this very small charset whereas a web server can use UTF-8? I don't think that using backslashreplace on stdout is a good idea. > But >PYTHONIOENCODING=mbcs > is al

[issue6501] Fatal error on startup with invalid PYTHONIOENCODING

STINNER Victor added the comment: > Fatal Python error: Py_Initialize: can't initialize sys standard streams > LookupError: unknown encoding: cp0 That's a bug in os.device_encoding(): os.device_encoding(sys.stdout.fileno()) should return None if the application has no console (if sys.stdout is

[issue6501] Fatal error on startup with invalid PYTHONIOENCODING

Daniel Goertzen 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 wo

[issue6501] Fatal error on startup with invalid PYTHONIOENCODING

Changes by Anthony Tuininga : -- nosy: +atuining ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue6501] Fatal error on startup with invalid PYTHONIOENCODING

Daniel Goertzen added the comment: I run into this problem when I start a Python app as a subprocess from Erlang (open_port() function). The PYTHONIOENCODING fix works when I launch my py app via pythonw.exe, but it does *not* work when I use the cx-freeze version of the app. I am using the

[issue6501] Fatal error on startup with invalid PYTHONIOENCODING

Changes by Éric Araujo : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/

[issue6501] Fatal error on startup with invalid PYTHONIOENCODING

Alexander Belopolsky added the comment: The issue is not Windows specific, so I am changing the title to reflect that. On OSX, for example, I get $ PYTHONIOENCODING=xyz ./python.exe Fatal Python error: Py_Initialize: can't initialize sys standard streams LookupError: unknown encoding: xyz Ab