Traceback messages too complicated (especially on doctests)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Try a doctest example, making some mistakes
2. Alternatively, type in a code sample that creates a traceback

What is the expected output? What do you see instead?

The output is pretty much the standard Python traceback, which is rather
unfriendly to beginner and likely an overkill even for advanced users,
given Crunchy's purpose (it is not intended as a development environment to
run complex applications - even though it could).

The old crunchy (0.8.2) had a simplified traceback handler.  We could
probably adapt it for the new Crunchy.

Original issue reported on code.google.com by andre.ro...@gmail.com on 7 Jul 2007 at 2:10

[GoogleCodeExporter]

Specifying milestone

Original comment by andre.ro...@gmail.com on 7 Jul 2007 at 2:18

• Added labels: Milestone-Release0.9

[GoogleCodeExporter]

Implemented for doctests (provided the user enters some valid Python code).  
Probably
sufficient for Release 0.9.

Original comment by andre.ro...@gmail.com on 9 Jul 2007 at 3:10

[GoogleCodeExporter]

Implemented for all.  Exists as the default option, switchable to something 
like the
regular tracebacks.

Original comment by andre.ro...@gmail.com on 23 Jul 2007 at 12:00

• Changed state: Fixed