[issue29546] A more helpful ImportError message

Changes by Donald Stufft : -- pull_requests: +987 ___ Python tracker ___ ___

[issue29546] A more helpful ImportError message

Barry A. Warsaw added the comment: New changeset 1bc156430bad8177b5beecf57979628c1d071230 by Barry Warsaw (Matthias Bussonnier) in branch 'master': bpo-29546: Improve from-import error message with location (#103)

[issue29546] A more helpful ImportError message

Changes by Serhiy Storchaka : -- pull_requests: -615 ___ Python tracker ___ ___

[issue29546] A more helpful ImportError message

Changes by Larry Hastings : -- pull_requests: +615 ___ Python tracker ___ ___

[issue29546] A more helpful ImportError message

Changes by Barry A. Warsaw : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___

[issue29546] A more helpful ImportError message

Changes by Ivan Levkivskyi : -- nosy: +levkivskyi ___ Python tracker ___ ___

[issue29546] A more helpful ImportError message

Matthias Bussonnier added the comment: See https://github.com/python/cpython/pull/103 that implements Barry's proposed format. -- ___ Python tracker ___

[issue29546] A more helpful ImportError message

Changes by Matthias Bussonnier : -- pull_requests: +66 ___ Python tracker ___

[issue29546] A more helpful ImportError message

Matthias Bussonnier added the comment: I'm unsure I understand changing only the default __str__() method. You will anyway have to format the message differently depending on whether you raise from a from-import or a from-import-* or any other locations. AFAIU you "just" need the following

[issue29546] A more helpful ImportError message

Brett Cannon added the comment: Thanks to Matthias' PR the information is all there in the exception, but the message has not been changed. One idea for this -- depending on how much C code you want to write -- is to provide a default message for __str__() that changes depending on whether

[issue29546] A more helpful ImportError message

Brett Cannon added the comment: New changeset bc4bed440504597cac47d0a215ee094bfa99ba7e by Brett Cannon in branch 'master': bpo-29546: Set 'path' on ImportError for ``from ... import ...`` (GH-91) https://github.com/python/cpython/commit/bc4bed440504597cac47d0a215ee094bfa99ba7e --

[issue29546] A more helpful ImportError message

Changes by Matthias Bussonnier : -- pull_requests: +62 ___ Python tracker ___

[issue29546] A more helpful ImportError message

Changes by Matthias Bussonnier : -- pull_requests: +62, 63, 64 ___ Python tracker ___

[issue29546] A more helpful ImportError message

Changes by Matthias Bussonnier : -- pull_requests: +62, 63 ___ Python tracker ___

[issue29546] A more helpful ImportError message

Matthias Bussonnier added the comment: Unsure if GitHub PR autolinks here. I'm attempting part of that at https://github.com/python/cpython/pull/91 AFAICT with my little knowledge of CPython internal, `name` and `path` where unset for `from ... import`. I'll be happy to change the

[issue29546] A more helpful ImportError message

Changes by Brett Cannon : -- type: -> enhancement ___ Python tracker ___ ___

[issue29546] A more helpful ImportError message

Brett Cannon added the comment: So 'path' already exists on ImportError so tweaking the message when the path is known wouldn't be difficult (https://docs.python.org/3/library/exceptions.html?highlight=importerror#ImportError). -- nosy: +brett.cannon

[issue29546] A more helpful ImportError message

New submission from Barry A. Warsaw: I haven't really thought about this deeply but I've observed that there are lots of cases where a user will report getting an ImportError trying to import a name from a module, where it turns out that the problem is that the module is coming from an