On Saturday 07 January 2006 02:17, WSobczuk wrote: > 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. > > 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??
If it were me, I'd get all this crap worked out on a staging server first with thorough testing. In other words, minimize the amount of broken code you publish and you won't have to worry about 10,000 emails telling you you screwed up. Really, this shouldn't be an issue in a production environment. As far as logging goes, Python has a nice logging facility that allows you to write to stdout, log files (with log file rotation), to a database and to email (is it *that* hard to find it yourself?): <http://docs.python.org/lib/module-logging.html> or import logging help(logging) or google or ... I suggest less whining and more reading. Eric.
