Django and framework logging
Quoth Bruce Kroeze:
One thing I just don’t understand is why more people, especially framework designers, omit or skip logging. Django appears to, which is incredibly annoying to me. It is a complex framework, which makes all kinds of assumptions and relies on convention to infer a lot of functionality. That’s great, but being able to “turn up” the log-level and see some discussion about what decisions it is making, based on what criteria it is using would be incredibly valuable to me. Not only to me, I wager, but to everyone who is learning the framework, or who is teasing out a difficult bug. Yet going in and adding framework-level logging is almost impossible, even on an open-source project, since your changes will not be accepted and will quickly become a merge nightmare.
I only skimmed through the Django tutorial and never really gave it the time it deserves, so I can’t say much about Django’s logging mechanisms (or lack thereof). But Bruce cites his bug report and doesn’t sound happy.
January 24th, 2006 at 7:46 am
Hi.. I’m only starting to use django, but I still find it quite easy to comprehend. It is great to have the sources of the methods and classes at hand while debugging. It replaces the need to log in debug purposes (imho)..