This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Suzumizaki
Recipients Suzumizaki
Date 2009-05-25.01:56:53
SpamBayes Score 2.791899e-10
Marked as misclassified No
Message-id <1243216616.61.0.580341646155.issue6102@psf.upfronthosting.co.za>
In-reply-to
Content
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)
Python: 3.0.1

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.
History
Date User Action Args
2009-05-25 01:56:56Suzumizakisetrecipients: + Suzumizaki
2009-05-25 01:56:56Suzumizakisetmessageid: <1243216616.61.0.580341646155.issue6102@psf.upfronthosting.co.za>
2009-05-25 01:56:54Suzumizakilinkissue6102 messages
2009-05-25 01:56:53Suzumizakicreate