The Basics
It is really useful to know what your Django project is doing, especially when debugging.
If you’re running Django via runserver, then you can simply use print statements and they will appear in the console. If you’re running via mod_python, then you can output the print statements to the web server’s error log by redirecting to stdout (print >> sys.stdout).
While useful, these both have their limitations. Python had a built-in logging system, so django-logging was created to allow it to be easily used within Django projects.
Project Home – http://code.google.com/p/django-logging/Grab the Repository – svn checkout http://django-logging.googlecode.com/svn/trunk/
Recent Commits
-
42 was committed 4 months, 2 weeks ago.
Fixed issue 27 — added SuppressLoggingOnAjaxRequestsMiddleware to help automatically suppress the output on AJAX requests. Thanks Marius Eriksen.
-
41 was committed 4 months, 2 weeks ago.
Fixed issue 26 — code introspection should now work with symlinks. Thanks Nowell Strite.
-
40 was committed 4 months, 2 weeks ago.
Fixed issue 25 — improved the text wrapping of SQL and removed the sqlite lexer as it didn’t work very well.
-
39 was committed 6 months ago.
Fixed issue 24 — frame inspection of SQL messages now work as expected, plus some refactoring of the “meaningful” frame code; thanks Nowell Strite.
-
36 was committed 6 months ago.
Fixed issue 23 — added support for LOGGING_REWRITE_CONTENT_TYPES; thanks nivlac.
-
35 was committed 6 months ago.
Fixed issue 21 by correcting the typo. Thanks Jeff.
-
33 was committed 9 months, 4 weeks ago.
Removed escape filter which was causing problems in Django 0.96. This is OK as the variable is escaped within the Python code.
-
32 was committed 9 months, 4 weeks ago.
Reapplying r30, which got overwritten by r31.
-
31 was committed 9 months, 4 weeks ago.
Fixed issue 18 — Added Pygments syntax highlighting and source code frame inspection. Thanks to donnex for the idea.
-
30 was committed 10 months ago.
Fixed issue 17 by replacing the % with %