default error message
Bug #125969 reported by
Wim Boucquaert
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| grok |
Fix Released
|
Low
|
Michael Haubenwallner | ||
| 1.0 |
Fix Released
|
Low
|
Michael Haubenwallner | ||
Bug Description
By default you always get a "a system error occurred" message it would be nice to have a nice traceback.
Eval Exception cfr Philikon's talk would be nice
Revision history for this message
| Philipp von Weitershausen (philikon) wrote | #1 |
| Changed in grok: | |
| assignee: | nobody → faassen |
| milestone: | none → 1.0 |
Revision history for this message
| Martijn Faassen (faassen) wrote | #2 |
| Changed in grok: | |
| assignee: | faassen → d2m |
| importance: | Undecided → Low |
Revision history for this message
| Michael Haubenwallner (d2m) wrote | #3 |
Revision history for this message
| Martijn Faassen (faassen) wrote | #4 |
To post a comment you must log in.
We could tackle this by plugging in a different SystemError exception view that displays the traceback. Zope 3 in fact has such a view already, registered in the DebugLayer (zope.app.debug or something).
Another way we can tackle this (Wim mentions this) is to use Paste and z3c.evalexception. Then you will get the normal safe behaviour if you don't use this middleware and you will get the interactive debugger when you do use it. We could enable the middleware by default.