[issue5376] Wrong ImportError message if module is not readable

Georg Brandl added the comment: Since this is not supported anyway (and never was), closing as "won't fix". -- nosy: +georg.brandl resolution: -> wont fix status: open -> closed ___ Python tracker

[issue5376] Wrong ImportError message if module is not readable

STINNER Victor added the comment: Oooh, import by filename has been disabled in Python 2.6: see issue #1776. ___ Python tracker ___ ___ Python

[issue5376] Wrong ImportError message if module is not readable

STINNER Victor added the comment: Oops, my first .tar.gz doesn't create files in a subdirectory. New archive fixes that. Added file: http://bugs.python.org/file13193/issue5376.tar.gz ___ Python tracker ___

[issue5376] Wrong ImportError message if module is not readable

Changes by STINNER Victor : Removed file: http://bugs.python.org/file13190/test.tar.gz ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue5376] Wrong ImportError message if module is not readable

New submission from STINNER Victor : __import__() raises an ImportError "No module named ..." if the module file is not readable or module directory is not executable. The expected message is something like "Module named ... is not readable". Directory tree for the test: --