Message90746
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 ;) |
|
Date |
User |
Action |
Args |
2009-07-20 23:25:36 | r.david.murray | set | recipients:
+ r.david.murray, brett.cannon |
2009-07-20 23:25:36 | r.david.murray | set | messageid: <1248132336.74.0.887815780927.issue6526@psf.upfronthosting.co.za> |
2009-07-20 23:25:35 | r.david.murray | link | issue6526 messages |
2009-07-20 23:25:35 | r.david.murray | create | |
|