| Version 5 (modified by , 15 years ago) ( diff ) |
|---|
Integrating Python's standard library logging module with Django
Mailing list proposal and discussion: http://groups.google.com/group/django-developers/browse_thread/thread/8551ecdb7412ab22
Python Logging 101: http://plumberjack.blogspot.com/2009/09/python-logging-101.html
Current code: http://github.com/simonw/django/tree/logging - tracked in ticket #12012
The Plan
- DONE: Create a 'django' logger, hooked up to a NullHandler and with propagate=False so all logging is silent by default
- Start using loggers within Django itself (so far only the SQL logger is DONE, and that implementation could definitely be improved)
- DONE: Add a --loglevel command line switch to ./manage.py runserver to cause specified handlers to print to the console
- DONE: Add a mechanism for configuring loggers from Django's settings.py file using a LOGGING setting
- Figure out how users can get fine-grained control over their loggers by writing regular Python code
Items marked DONE above aren't necessarily of production quality yet, but there's enough working code to see how they would look.
Logging from concurrent processes
If you're running logging within something like mod_wsgi or mod_python you can't just log straight to a file due to the need to handle multiple processes. Under mod_wsgi logging to stderr will cause log messages to end up in the Apache error log. If that's not good enough for you, consider the following options for logging from concurrent processes:
- Using SocketServer: http://www.huyng.com/archives/418
- Using file locking: http://pypi.python.org/pypi/ConcurrentLogHandler/