#33860: When debug level == DEBUG, loading admin page causes a voluminous 
exception
message to be emitted in logging
---------------------------------+--------------------------------------
     Reporter:  Andrew Selby     |                    Owner:  (none)
         Type:  Bug              |                   Status:  closed
    Component:  Error reporting  |                  Version:  4.0
     Severity:  Normal           |               Resolution:  duplicate
     Keywords:                   |             Triage Stage:  Unreviewed
    Has patch:  0                |      Needs documentation:  0
  Needs tests:  0                |  Patch needs improvement:  0
Easy pickings:  0                |                    UI/UX:  0
---------------------------------+--------------------------------------

Comment (by Andrew Selby):

 Replying to [comment:1 Mariusz Felisiak]:

 Thanks for the quick reply.

 I'm perfectly aware that log levels can be used to adjust what log
 messages I see, the point is that I want to be able to use all levels of
 logging to develop, debug and test my own code which uses the Django
 framework. When I'm debugging, I lower the debug level, when it's running
 smoothly I raise it. This kind of pollution from Django internals impedes
 my ability to fully use the debug levels when developing my own code.

 The logger message that was raised was not something I could take any
 meaningful action on, or that was likely to be of any use to an informed
 user. Should logging be used to debug the code using the framework, or to
 debug the framework itself? Your answer implies that the logging should be
 used to debug Django itself (ie, for the benefit of the developers), which
 makes logging a less clean and therefore useful feature for code using the
 framework. This is a major philosophical mistake. Who is Django intended
 for - the Django developers, or for the Django users?

 An additional problem is, why is an exception trace from an internally
 handled exception being dumped into the logs? This should just not happen.

 It looks like the Django 4.1+ fix ensures that the exception does not get
 thrown, so I'm hopeful that will avoid the specific problem I had - I see
 it's due out in a few weeks!

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33860#comment:2>
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701821fa622d1-65527ef6-0926-4b57-b839-72934ed42b19-000000%40eu-central-1.amazonses.com.

Reply via email to