This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients brett.cannon, r.david.murray
Date 2009-07-20.23:25:35
SpamBayes Score 2.04397e-09
Marked as misclassified No
Message-id <>
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:36r.david.murraysetrecipients: + r.david.murray, brett.cannon
2009-07-20 23:25:36r.david.murraysetmessageid: <>
2009-07-20 23:25:35r.david.murraylinkissue6526 messages
2009-07-20 23:25:35r.david.murraycreate