#25684: Runserver doesn't use `LOGGING` configuration
-----------------------------------+------------------------------------
Reporter: fcurella | Owner: fcurella
Type: New feature | Status: assigned
Component: Error reporting | Version: master
Severity: Normal | Resolution:
Keywords: runserver logging | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Comment (by timgraham):
I have some concerns that anyone
[https://docs.djangoproject.com/en/1.9/topics/logging/#disabling-logging-
configuration disabling logging] will be confused why `runserver` doesn't
log anymore. They'll need instructions for how to reenable it. Do the
benefits of this change outweigh the costs to these users?
If we end up replacing the `runserver` machinery with something like
gunicorn (#21978), I wonder if the logging situation would change again
(i.e. would our version of `WSGIRequestHandler` be obsolete?). I don't
know how close that change is to happening (maybe it will never happen),
but I just wanted to raise these points for consideration so we can focus
our time and avoid needlessly annoying our users by making conflicting
changes in one area over several consecutive releases.
--
Ticket URL: <https://code.djangoproject.com/ticket/25684#comment:34>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.babb7123e1d542281f1bb7722d77e04e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
