[issue3619] A more informative message for ImportError

Brett Cannon added the comment: Closing as "won't fix" as this assumes that path information is applicable to all importers which is not correct. -- resolution: -> wont fix status: open -> closed ___ Python tracker

[issue3619] A more informative message for ImportError

Changes by Daniel Diniz : -- assignee: -> brett.cannon nosy: +brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue3619] A more informative message for ImportError

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- components: +Interpreter Core -None priority: -> low versions: +Python 3.1 ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3619] A more informative message for ImportError

New submission from Kent Tenney <[EMAIL PROTECTED]>: from foo import bar ImportError: cannot import name bar The error may be due to the wrong 'foo' being found, some investigation is required. If the the ImportError message included the filename for 'foo', the problem would be obvious. ImportE