Get rid of vague or imprecise error messages from tests

[GoogleCodeExporter]

This is an open issue, please post any error messages coming from the new 
test framework which you would like to make more precise and/or user-
friendly before pygr-0.8 is released.

Original issue reported on code.google.com by mare...@gmail.com on 26 Mar 2009 at 7:24

[GoogleCodeExporter]

If runtest.py is launched without the option -b and no in-place-build files can 
be 
found, it responds with

ERROR pathfix.stop: unable to import extension module: cannot import name 
cnestedlist

Given this error will likely be run into almost all end users trying to run 
tests, 
such a cryptic response is unacceptable. I would like to postulate the 
following 
steps to be taken to address this:

1. Whenever runtest.py is launched, have it clearly and explicitly say where it 
pulls Pygr files from (this will also help for when -b is omitted with stale in-
place-build files in place);

2. Make the actual error message more descriptive;

3. Consider making in-place testing an option rather than the default, at least 
in 
official release packages.

Original comment by mare...@gmail.com on 26 Mar 2009 at 7:31

[GoogleCodeExporter]

Original comment by mare...@gmail.com on 27 Mar 2009 at 12:53

[GoogleCodeExporter]

Original comment by cjlee...@gmail.com on 8 Apr 2009 at 2:00

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

See issue #85.

Original comment by the.good...@gmail.com on 26 Apr 2009 at 8:41

[GoogleCodeExporter]

The problem reported in comment #1 has since been fixed and no other issues of 
the sort 
have been found pertinent. Therefore, the issue is now closed.

Original comment by mare...@gmail.com on 25 Jun 2009 at 1:22

• Changed state: Closed