""Martin v. Löwis"" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] |> Now, why don't we change the semantics as follows: if a file with matching name | > exists (in import.c::find_module), but opening fails, ImportError is raised | > immediately with the concrete error message, and without trying the rest of | > sys.path. That shouldn't cause any working and sane setup to break, or did I | > overlook something obvious here? | | I wonder how this would behave if a directory on sys.path was | unreadable.
I understood Brett to be talking about a different case where the directory *is* readable and the target file shows up in the directory list. In this limited case, stopping seems sane to me. | You might get an ImportError on *any* import, as | it tries the unreadable directory first, gets a permission error, | and immediately aborts. Not if the patch is properly and narrowly written to only apply to unreadable files in readable directories. tjr
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
