[Import-SIG] improving ImportError

[Brett Cannon]

On Wed, Sep 21, 2011 at 12:06, Eric Snow <ericsnowcurrently at gmail.com>wrote:

> Armin Ronacher has an interesting blog post about some of the
> challenges of using Python's imports:
>
> http://lucumr.pocoo.org/2011/9/21/python-import-blackbox/
>
> In particular, his main point about "not found" vs. "broken" vs.
> "problem with inner import" got me thinking.  Would it be a bad idea
> to split ImportError into more specific exceptions?  I imagine that
> cataloguing the different causes of ImportError and how someone might
> react to those differently wouldn't be too hard...
>

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: http://bugs.python.org/issue1559549 .
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/import-sig/attachments/20110921/e385de4d/attachment.html>