errors importing commands are obfuscated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Testrepository |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
affects testrepository
When running testrepository without python-fixtures installed I get a
strange error:
$ testr run
Traceback (most recent call last):
File "/usr/bin/testr", line 26, in <module>
sys.
File
"/usr/lib/
line 178, in run_argv
cmdclass = _find_command(
File
"/usr/lib/
line 49, in _find_command
raise KeyError("Could not import command module %s" % modname)
KeyError: 'Could not import command module testrepository.
Commenting out the exception handling I get:
Traceback (most recent call last):
File "/usr/bin/testr", line 26, in <module>
sys.
File
"/usr/lib/
line 175, in run_argv
cmdclass = _find_command(
File
"/usr/lib/
line 46, in _find_command
_temp = __import__(modname, globals(), locals(), [classname])
File
"/usr/lib/
27, in <module>
from testrepository.
File "/usr/lib/
line 18, in <module>
from fixtures import Fixture
ImportError: No module named fixtures
It'd be nice if testrepository could give a saner error when fixtures
was missing.
Changed in testrepository: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
summary: |
- clearer error when fixtures is missing + exception reporting is so brief problems cannot be diagnosed easily. |
summary: |
- exception reporting is so brief problems cannot be diagnosed easily. + errors importing commands are obfuscated |
You can set TESTR_PDB=1 to diagnose this.