Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > Python > wrong ImportError message printed by python3.3 when it can't finda module?

Reply
Thread Tools

wrong ImportError message printed by python3.3 when it can't finda module?

 
 
Irmen de Jong
Guest
Posts: n/a
 
      12-07-2012
Hi,

I'm seeing that Python 3.3.0 is not printing the correct ImportError when it can't
import a module that is imported from another module. Instead of printing the name of
the module it can't import, it prints the name of the module that is doing the faulty
import.

Behold:
I have created:
importfail\
__init__.py
main.py
sub.py


[L:\]type importfail\main.py
from . import sub

[L:\]type importfail\sub.py
import nonexisting_module

[L:\]


[L:\]c:\Python33\python.exe -m importfail.main
Traceback (most recent call last):
File "C:\Python33\lib\runpy.py", line 160, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "C:\Python33\lib\runpy.py", line 73, in _run_code
exec(code, run_globals)
File ".\importfail\main.py", line 1, in <module>
from . import sub
ImportError: cannot import name sub # <--- huh ?


Python 3.2 and earlier do the right thing:

[L:\]c:\Python32\python.exe -m importfail.main
Traceback (most recent call last):
File "C:\Python32\lib\runpy.py", line 160, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "C:\Python32\lib\runpy.py", line 73, in _run_code
exec(code, run_globals)
File "L:\importfail\main.py", line 1, in <module>
from . import sub
File "importfail\sub.py", line 1, in <module>
import nonexisting_module
ImportError: No module named nonexisting_module # <--- ok.

(this is on windows, but on osx I see the same behavior).


Is there a problem with the rewritten import logic in Python 3.3?

Thanks
Irmen de Jong
 
Reply With Quote
 
 
 
 
Peter Otten
Guest
Posts: n/a
 
      12-07-2012
Irmen de Jong wrote:

> I'm seeing that Python 3.3.0 is not printing the correct ImportError when
> it can't import a module that is imported from another module. Instead of
> printing the name of the module it can't import, it prints the name of the
> module that is doing the faulty import.
>
> Behold:
> I have created:
> importfail\
> __init__.py
> main.py
> sub.py
>
>
> [L:\]type importfail\main.py
> from . import sub
>
> [L:\]type importfail\sub.py
> import nonexisting_module
>
> [L:\]
>
>
> [L:\]c:\Python33\python.exe -m importfail.main
> Traceback (most recent call last):
> File "C:\Python33\lib\runpy.py", line 160, in _run_module_as_main
> "__main__", fname, loader, pkg_name)
> File "C:\Python33\lib\runpy.py", line 73, in _run_code
> exec(code, run_globals)
> File ".\importfail\main.py", line 1, in <module>
> from . import sub
> ImportError: cannot import name sub # <--- huh ?
>
>
> Python 3.2 and earlier do the right thing:
>
> [L:\]c:\Python32\python.exe -m importfail.main
> Traceback (most recent call last):
> File "C:\Python32\lib\runpy.py", line 160, in _run_module_as_main
> "__main__", fname, loader, pkg_name)
> File "C:\Python32\lib\runpy.py", line 73, in _run_code
> exec(code, run_globals)
> File "L:\importfail\main.py", line 1, in <module>
> from . import sub
> File "importfail\sub.py", line 1, in <module>
> import nonexisting_module
> ImportError: No module named nonexisting_module # <--- ok.
>
> (this is on windows, but on osx I see the same behavior).


A paragon of clarity -- ye lurkers, this is how a bug report should be.

> Is there a problem with the rewritten import logic in Python 3.3?
>
> Thanks
> Irmen de Jong


I believe this is fixed, see http://bugs.python.org/issue15111



 
Reply With Quote
 
 
 
 
Irmen de Jong
Guest
Posts: n/a
 
      12-07-2012
On 7-12-2012 22:20, Peter Otten wrote:

> A paragon of clarity -- ye lurkers, this is how a bug report should be.




>
>> Is there a problem with the rewritten import logic in Python 3.3?
>>
>> Thanks
>> Irmen de Jong

>
> I believe this is fixed, see http://bugs.python.org/issue15111


Argh, why didn't I search the bug tracker first: I would have found that one for sure.
Anyway, thanks for pointing it out.

The bug is confusing but it doesn't break anything so far. I guess I'll be fine waiting
for 3.3.1.


Irmen

 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Suggestion for improved ImportError message Kent Tenney Python 6 08-23-2008 05:08 PM
The Famous Error Message: "ImportError: No module named python_script" rich murphy Python 12 12-15-2006 06:51 AM
JNI, Python ImportError Tero Pihlajakoski Java 2 02-11-2004 11:24 AM
Re: newbie question: ImportError: No module named Numeric Mikael Olofsson Python 0 07-16-2003 06:46 AM
Re: newbie question: ImportError: No module named Numeric Harry George Python 0 07-15-2003 07:18 PM



Advertisments