R. David Murray <rdmur...@bitdance.com> added the comment: Oh, a bit of clarification: the call that creates the pyc file in both the "normal" case and the error case is a call to the normal import command (or __import__ in the test case). The call to import_module is a prereq to producing the bug, but it doesn't matter what module it imports (as long as it hasn't been previously imported). The import that shows the behavior imports a TESTFN module in the test case.
You might want to load up the test case and play with it. I'm completely mystified as to how import_module could be affecting the regular import semantics...I'm guessing it is a subtle side effect of something unexpected ;) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6526> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
