Hyeshik Chang added the comment:
Hello, everyone!
The rationale why I chose to encode the test strings into a Python source code
was that I wanted for them to be treated as text files which are trackable in
CVS or subversion and to keep Python source codes free of any non-ASCII
characters
Changes by Hyeshik Chang :
--
title: Interpreter fails to initialize when IO encoding is one of CJK on build
dir -> Interpreter fails to initialize on build dir when IO encoding is one of
CJK
___
Python tracker
<http://bugs.python.org/iss
New submission from Hyeshik Chang :
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 enc
Changes by Hyeshik Chang :
Removed file: http://bugs.python.org/file13572/cjkcodecs-fix-statefulenc.diff
___
Python tracker
<http://bugs.python.org/issue5640>
___
___
Hyeshik Chang added the comment:
Uploaded a revised patch that solved the newer problem.
--
Added file: http://bugs.python.org/file13573/cjkcodecs-fix-statefulenc-2.diff
___
Python tracker
<http://bugs.python.org/issue5