<br><br><div class="gmail_quote">On Wed, Sep 21, 2011 at 12:06, Eric Snow <span dir="ltr"><<a href="mailto:ericsnowcurrently@gmail.com">ericsnowcurrently@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Armin Ronacher has an interesting blog post about some of the<br>
challenges of using Python's imports:<br>
<br>
<a href="http://lucumr.pocoo.org/2011/9/21/python-import-blackbox/" target="_blank">http://lucumr.pocoo.org/2011/9/21/python-import-blackbox/</a><br>
<br>
In particular, his main point about "not found" vs. "broken" vs.<br>
"problem with inner import" got me thinking. Would it be a bad idea<br>
to split ImportError into more specific exceptions? I imagine that<br>
cataloguing the different causes of ImportError and how someone might<br>
react to those differently wouldn't be too hard...<br></blockquote><div><br></div><div>Without reading the blog post, granularity never hurt. But first thing is first, I need to get an attribute or two on ImportError to help identify what has gone wrong: <a href="http://bugs.python.org/issue1559549">http://bugs.python.org/issue1559549</a> . </div>
</div>