[issue41154] test_pkgutil:test_name_resolution fails on some platforms

Brett Cannon added the comment: I wonder if it's a problem from Unicode representation since I don't think importlib tries to have a standard normalization form of Unicode. I could see that leading to how the file system encoded something differing from how it was encoded in the test file,

[issue41154] test_pkgutil:test_name_resolution fails on some platforms

Vinay Sajip added the comment: The problem appears to be in importlib. I put in a breakpoint in the test just before it tries to import the module é. (At this point it has successfully imported a module called वमस in an earlier loop iteration.) Then, in a different terminal console, I cd'd

[issue41154] test_pkgutil:test_name_resolution fails on some platforms

Change by STINNER Victor : -- nosy: -vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41154] test_pkgutil:test_name_resolution fails on some platforms

Change by Florian Bruhin : -- nosy: +The Compiler ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41154] test_pkgutil:test_name_resolution fails on some platforms

Ned Deily added the comment: PS, the problem may have been introduced by the changes for bpo-12915. -- ___ Python tracker ___ ___

[issue41154] test_pkgutil:test_name_resolution fails on some platforms

Ned Deily added the comment: This same failure is observed with the most recent 3.9beta (3.9.0b3) when running on macOS 10.9 with the binaries from the python.org macOS installer. However, no failure is seen when running the same Python on macOS 10.15. I have not investigated further with