Message165186
| Author |
brett.cannon |
| Recipients |
amaury.forgeotdarc, brett.cannon, chris.jerdonek, r.david.murray |
| Date |
2012年07月10日.13:07:58 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1341925680.4.0.472277266343.issue15111@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
That "cannot import name" message seems to only come from Python/ceval.c:import_from() which raises that exception when an AttributeError is raised by an 'import from' statement (I think). This happens when an 'import from' asks for a name on the package/module that doesn't exist.
Looking at importlib, I found the code that captures the ImportErrorof a submodule, which allows the import to continue and then fail as an AttributeError at the bytecode level. I'm running the test suite now with that try/except removed to see if this was just a mis-interpretation on my part of how to handle this situation. As of right now the only failures I have continue my belief that import * is evil. |
|