Hm, now I wonder if that blog post in my initial post is entirely correct.
This config seems to send all Django logging to stdout (regardless of the
value of disable_existing_loggers). The difference from the initially
proposed doc patch is that this config redefines the 'django' logger
instead of the 'root' logger. Investigation to continue tomorrow...
LOGGING = {
'version': 1,
'disable_existing_loggers': False,
'handlers': {
'console': {
'class': 'logging.StreamHandler',
},
},
'loggers': {
'django': {
'handlers': ['console'],
'level': 'DEBUG',
},
}
}
On Monday, March 23, 2015 at 5:06:39 PM UTC-4, Florian Apolloner wrote:
>
> On Monday, March 23, 2015 at 9:45:12 PM UTC+1, Wim Feijen wrote:
>>
>> This may sound stupid, but I actually use Logbook for logging because I
>> find it easy to use.
>>
>
> Why would this sound stupid? Logbook is a nice library and actually worth
> thinking about if we start using dependencies in Django.
>
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/8030352a-f072-4646-8b3a-a1a2fcad1b35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
