>I'm not saying I wnat to send information to users, I'm saying I want >it logged (at least to stdout is it *that* hard?). And I'm not keen on >putting down my email server when I publish some broken code and get >10000 error emails. Email isn't a means of error reporting - logs are.
The only measures on "logging errors in production systems" currently readily implemented _is_ sending them by email to the admins (or some other account that's set up solely for that purpose). The only other means I know to catch view function errors is to add a middleware that uses the process_exception hook to handle the exception and to write it out to some log file or to syslog or whatever. Shouldn't be too hard to write, and since it would only provide a process_exception hook, it wouldn't put any additional load on the normal requests. >And digging through templates isn't really my idea of debugging. Is it >really so hard to print what template was the one in which the error >occurred?? Of course not - that's what the template debugging stuff does. But that is limited to TEMPLATE_DEBUG=True. You might be able to check with the template debugging stuff to see how rjwittams does it and rebuild part of that in the mentioned process_exception hook to log the template origin. Or wait until rjwittams returns and ask him wether he has some idea on how to accomplish that. bye, Georg
