New submission from Jean-Paul Calderone <[email protected]>:
If pydoc is used to try to look up the documentation for a module which
does not exist, this is reported reasonably:
exar...@charm:~$ pydoc foobarbaz
no Python documentation found for 'foobarbaz'
exar...@charm:~$
However, if it is used to look up the documentation for a module which
does exist but which itself imports a module which does not exist, then
the same report is made:
exar...@charm:~$ cat > foobarbaz.py
import barbazquux
exar...@charm:~$ pydoc foobarbaz
no Python documentation found for 'foobarbaz'
exar...@charm:~$
This is somewhat misleading, since it suggests that there is no such
module "foobarbaz", when the problem is solved by installing the module
"barbazquux":
exar...@charm:~$ touch barbazquux.py
exar...@charm:~$ pydoc foobarbaz
Help on module foobarbaz:
...
exar...@charm:~$
I'm sure the cause of this is the incautious handling of ImportError by
pydoc, resulting in the mistaken identification of the problem.
----------
messages: 81821
nosy: exarkun
severity: normal
status: open
title: pydoc reports misleading failure if target module raises an ImportError
type: behavior
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue5230>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
