#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: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Changes (by carljm):
* stage: Unreviewed => Accepted
Comment:
I've always wondered why the runserver output didn't use logging; it seems
like an obvious candidate for it. I may be missing something (in which
case hopefully someone else will chime in), but it seems to me that option
(a) -- replace `stderr.write(...)` with logging calls, and adjust the
default logging config so they are still shown -- is the right one.
One reason I can think of why perhaps this hasn't been done is the color
used to mark different response status codes in the runserver output? I
would think it should be possible to preserve that with the right custom
logging handler, though.
--
Ticket URL: <https://code.djangoproject.com/ticket/25684#comment:6>
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.0281763d1e6c07af83cbcd2ba1f2f13b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
