[issue6102] When the package has non-ascii path and .pyc file, we cannot import them.

Terry J. Reedy added the comment: Am closing based on 'My problem seems resolved'. I don't know whether it will be fixed in 3.0.2 or not, but that is pretty much a moot point. -- nosy: +tjreedy resolution: -> fixed status: open -> closed ___ Python

[issue6102] When the package has non-ascii path and .pyc file, we cannot import them.

Suzumizaki added the comment: Thanks for reply. I tried Python 3.1 Beta, and the testcode goes fine. (and my current work also.) I checked with Windows XP, I told before. My problem seems resolved, and here is answers only to make sure. >(What is the value of sys.maxunicode there though?) 6

[issue6102] When the package has non-ascii path and .pyc file, we cannot import them.

Antoine Pitrou added the comment: Could you test with the 3.1 beta? There's a Windows installer here: http://python.org/download/releases/3.1/ -- nosy: +pitrou ___ Python tracker ___

[issue6102] When the package has non-ascii path and .pyc file, we cannot import them.

Ezio Melotti added the comment: Your problem could be related to #3297, but katakana characters don't have a codepoint greater than U+ so it could be something else. (What is the value of sys.maxunicode there though?) I tried your script on Linux with Python3.1b1 and en_US.UTF-8 but I wasn'

[issue6102] When the package has non-ascii path and .pyc file, we cannot import them.

New submission from Suzumizaki : 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