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
-
25 was committed 1 month, 4 weeks ago.
Fixed issue 12 — SQL logging should now work in Python 2.3. Thanks drennalls.
-
24 was committed 1 month, 4 weeks ago.
Fixed issue 11 — added some extra comments and tidied up the code a bit. Thanks Steve Milner.
-
22 was committed 1 month, 4 weeks ago.
Switched to Unix-style newlines throughout (see issue 11).
-
21 was committed 5 months, 1 week ago.
Updated copyright year in the licence file.
-
20 was committed 5 months, 1 week ago.
Added the ability to suppress logging output on particular views by using a decorator. Thanks to erikwickstrom for the idea.
-
19 was committed 7 months, 2 weeks ago.
Fixed minor indentation issue.
-
18 was committed 7 months, 2 weeks ago.
Fixed issue 9 — LOGGING_LOG_SQL now works in with Python 2.4.
-
17 was committed 8 months ago.
Fixed Issue 7 — _admin_path couldn’t be determined in some cases.
-
16 was committed 8 months, 4 weeks ago.
Fixed problem that occured when CommonMiddleware performed a redirect.
-
15 was committed 8 months, 4 weeks ago.
Fixed problem with intercepting redirects to relative URLs.