[issue7441] Py3.1: Fatal Python Error: Py_Initialize...unknown encoding: chcp 65001.

STINNER Victor added the comment: I added a cp65001 codec to Python 3.3: see issue #13216. So Python will not "crash" anymore if the console code page is set to cp65001. -- nosy: +haypo ___ Python tracker

[issue7441] Py3.1: Fatal Python Error: Py_Initialize...unknown encoding: chcp 65001.

Changes by Georg Brandl : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue7441] Py3.1: Fatal Python Error: Py_Initialize...unknown encoding: chcp 65001.

Florent Xicluna added the comment: Thank you for your report. See #6501 about the Fatal Error See #6058 for the feature request (cp65001 on windows). -- resolution: -> duplicate stage: -> committed/rejected superseder: -> Fatal LookupError: unknown encoding: cp0 on Windows embedded

[issue7441] Py3.1: Fatal Python Error: Py_Initialize...unknown encoding: chcp 65001.

flox added the comment: there's a patch proposed to add cp65001 alias: issue6058 -- nosy: +flox ___ Python tracker ___ ___ Python-bugs

[issue7441] Py3.1: Fatal Python Error: Py_Initialize...unknown encoding: chcp 65001.

New submission from Lie Ryan : maybe related to #6501 Vista 32-bit SP1, Python 3.1: """ Microsoft Windows [Version 6.0.6000] Copyright (c) 2006 Microsoft Corporation. All rights reserved. D:\>chcp 65001 Active code page: 65001 D:\>python -c 'print("")' Fatal Python error: Py_Initialize: can't