#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: 1
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Comment (by carljm):
The release notes should of course mention the change. I don't think we
need detailed instructions for how to re-enable it for people who may have
disabled the default logging config; it's enough to say (something like)
"runserver now logs each request to the `django.server` logger instead of
outputting it directly to console; if your logging config overrides
Django's defaults, see the default logging config (link) for an example of
how to configure runserver logging with color output."
Disabling Django's default logging config is an advanced usage, anybody
doing that should know enough about logging to configure things
appropriately from there. (And really, a manual logging config that
silently discards logging output from unknown loggers by default is kind
of broken; someone with such a setup shouldn't be surprised to be missing
some logging output.)
Also, we're talking about a development convenience here, not something
that breaks production code-paths, so the backwards-compatibility concern
level is lower.
I think the benefits of this change are major, in terms of added
flexibility to filter and customize runserver logging output without
needing to hack core Django code.
And any possibility of replacing runserver remains quite remote AFAICS --
there are a lot of hard questions there that remain unanswered, and I'm
not aware of anyone actively working on answering them. I certainly don't
think it's anywhere near imminent enough to provide justification for
halting all improvements to runserver.
So IMO this change is definitely worth moving forward.
--
Ticket URL: <https://code.djangoproject.com/ticket/25684#comment:36>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.216f8271a11e950665f2a12b46879481%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
