[New-bugs-announce] [issue6102] When the package has non-ascii path and .pyc file, we cannot import them.
report at bugs.python.org
Mon May 25 03:56:56 CEST 2009
New submission from Suzumizaki <suzumizaki at free.japandesign.ne.jp>:
When the path of the package has non-ascii characters, importing such
packages always fails except the first time (in other words, always
fails when compiled .pyc file exists).
The problem exists even the names of such modules only consist of
us-ascii characters. Please follow the test code I create, which can
test the problem even with English version Windows(, I expected).
Target: Windows XP (I tested Home Ed., SP3, 32bit, Japanase version)
The priority of this issue might be CRITICAL or higher by 2 reasons:
1) When the end-users meet this condition, the users cannot find what's
wrong easily, because UnicodeDecodeError is raised (not ImportError).
2) On non-English version Windows, "Desktop", "My Documents" or etc.
folders have non-English name as default. For example, Katakana is used
in Japanese version. This means all python packages in the desktop meet
this problem for not a few users.
title: When the package has non-ascii path and .pyc file, we cannot import them.
versions: Python 3.0
Added file: http://bugs.python.org/file14063/testcode.zip
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce