#12012: Integration with the Python standard library logging module
-------------------------------------+--------------------------------------
Reporter: simon | Owner: nobody
Status: new | Milestone:
Component: Core framework | Version: SVN
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 1
Needs_docs: 1 | Needs_tests: 1
Needs_better_patch: 1 |
-------------------------------------+--------------------------------------
Comment (by simon):
I might be going about the initialisation the wrong way then. Here's what
I want to achieve: without the user needing to do anything at all
(including modifying a settings.py created before logging was added to
Django) I want ALL messages to any logger beneath "django" to be silently
swallowed, no matter what the severity. My understanding is that the
correct way to do this is to hook up a NullHandler and set "propogate =
False" on the "django" logger as early as possible. Is there a better way
of achieving that?
--
Ticket URL: <http://code.djangoproject.com/ticket/12012#comment:3>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
