#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
-----------------------------------+------------------------------------
Comment (by carljm):
I don't actually see a performance concern mentioned there. There are
three concerns:
1. Adding complexity to out-of-the-box local-dev experience. I think this
is a non-issue, if the default logging config results in the same behavior
we have currently. No additional setup should be needed.
2. Losing colorization of devserver messages. I agree this would be a
problem, but as mentioned above we should be able to preserve this with a
custom formatter.
3. "It's a feature that can be achieved with pipes and grep" -- this
objection could apply to any use of the logging framework in Django. It
doesn't really make sense to allow much of Django's logging output to be
configured using Python's logging framework, but in this specific case
prevent that and require using totally different techniques instead.
--
Ticket URL: <https://code.djangoproject.com/ticket/25684#comment:13>
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.364c344b4d462ad046dcbf661cccc5c1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
