#30553: Misleading logging documentation about disable_existing_loggers default
     Reporter:  darthdragon          |                    Owner:  nobody
         Type:                       |                   Status:  new
  Cleanup/optimization               |
    Component:  Documentation        |                  Version:  master
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
  disable_existing_loggers logging   |
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  1                    |                    UI/UX:  0

Comment (by darthdragon):

 I think these two sentences are what may start the headache:

  "By default, the LOGGING setting is merged with Django’s default logging
 configuration using the following scheme.

  If the disable_existing_loggers key in the LOGGING dictConfig is set to
 True (which is the default) then all loggers from the default
 configuration will be disabled. ...

 Because even after reading it 10 times, if you have never looked to python
 logging.config (and I didn't until today, shame on me),  you may not
 understand that also any loggers that may have been defined before are
 also disabled.

 And maybe clarifying in "Django’s default logging configuration", that the
 default django loggers are added with disable_existing_loggers=False.

Ticket URL: <https://code.djangoproject.com/ticket/30553#comment:5>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to