I've seen some Internal Server Error and the full traceback is send to the client not handled by Django. For instance, I wrote a middleware using piston and every error 500 sent a normal Python backtrace only. Anyway, is it a Django bug?
I think the error 500 must be get caught by Django not Piston.
Former userAccount Deleted
I'm interested in being able to catch an exception that happens when a resource handler is running. Right now, they are trapped by Piston and either returned to the client or e-mailed to the admins. I would love to have what josemoreira is doing above, where the exception is logged first.
Specifically this would make running "./manage.py test" more useful, because the exception would actually be captured in the output if one occurred. Right now if a test fails, I have to re-run the query that cause it to see the error.