On Sun, 2007-04-22 at 20:28 +0000, Fraser Nevett wrote: > Hi All, > > I'm sure I'm not alone in using simple print statements to trace/log > what is going on in a Django app, especially when debugging. This > works OK when using runserver, but can be more difficult and > problematic to use with mod_python in a production environment. > > To try to give greater control and flexibility in logging, I have > created "django-logging", which uses Python's built-in logging module. > It logs messages on a per-request basis and then appends these to HTML > responses so that you can easily see what happened during that > request.
I agree with Jeremy, this is a nice contribution. Thanks for writing it. :-) I particularly like the way the design is very non-intrusive, having no effect at all when you are not using it. One minor point for when you want to do a point release: I think it would be worth shipping a copy of some documentation -- at least, how to use it -- with the code. I originally grabbed the download, went to look at it whilst on a train and discovered a complete lack of documentation because it expected me to be connected to the Internet. The whole planet does not have "always on" Internet yet (thankfully). Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
