#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 Mariusz Felisiak):
> 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.
That's why it was fixed.
> 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?
Removing logging for template variable resolving would be exactly the
opposite to what you say. Django users write templates as well as
overwrite and customize the templates used by admin.
> Your answer implies that the logging should be used to debug Django
itself ...
I've never said anything like that.
--
Ticket URL: <https://code.djangoproject.com/ticket/33860#comment:3>
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/010701821fadbb84-7837bd2c-1b46-4bbe-9008-17549eec8cb9-000000%40eu-central-1.amazonses.com.
