[issue5667] Interpreter fails to initialize when IO encoding is one of CJK on build dir
Hyeshik Chang
report at bugs.python.org
Thu Apr 2 11:25:40 CEST 2009
New submission from Hyeshik Chang <hyeshik at gmail.com>:
When a developer uses one of CJK encodings, interpreter crashes while
its initialization on build dir (not on installed base).
% LC_ALL=ko_KR.eucKR ./python
Fatal Python error: Py_Initialize: can't initialize sys standard streams
LookupError: unknown encoding: euc_kr
zsh: abort (core dumped) LC_ALL=ko_KR.eucKR ./python
The problem is that codec lookup function fails to import a relevant
codec module because path to dynamic modules is added by site.py, which
is a later step than standard I/O object initializations.
----------
components: Interpreter Core
messages: 85187
nosy: hyeshik.chang
priority: low
severity: normal
status: open
title: Interpreter fails to initialize when IO encoding is one of CJK on build dir
type: crash
versions: Python 3.1
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5667>
_______________________________________
More information about the Python-bugs-list
mailing list