New submission from Charles Mason <cemaso...@gmail.com>: Steps to reproduce:
1) Add to sys.path a path that does not exist 2) Import a module, any module. This invokes get_path_importer over every element of sys.path. The NullImporter __init__ method is called and an instance created for each non-existing path element in sys.path. 3) Create the path and put a valid module in said path 4) Try to import that module. Behavior is that the interpreter fails to import. This behavior seems local to import.c only. Attached a test case that shows "failed" for 2.5, 2.6, 3.0. 3.1rc1+. I have yet to test on the trunk but I can/will do that if necessary. I believe I can fix this myself but I want to verify this is incorrect behavior (a bug) and not an "Undocumented Feature" (or hell, maybe it *is* documented somewhere). I've skimmed over PEP 302 and didn't see any relevant information. If someone gives me the go ahead (or at least doesn't give me reason not to), I'll get a patch put together, perhaps for several different "fixes". ---------- components: Interpreter Core files: test.py messages: 91241 nosy: cemasoniv severity: normal status: open title: Non-existant directory in sys.path prevents further imports type: behavior versions: Python 2.5, Python 2.6, Python 3.0, Python 3.1 Added file: http://bugs.python.org/file14640/test.py _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6636> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com