#27234: Clarify the type of the django.server logger's 'request' extra context
-------------------------------------+-------------------------------------
Reporter: Ben Whale | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: 1.10
Severity: Normal | Resolution:
Keywords: django.request | Triage Stage: Accepted
runserver WSGIRequest socket |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
I don't think making `django.request` do the logging of `django.server` is
desirable. The purpose of having two loggers is to keep `runserver`
logging separate from other logging.
I don't have any strong feelings about your documentation proposal. I'm
sure there are plenty of apps out there that use Django logging for all
requests and I don't see any problems with that.
--
Ticket URL: <https://code.djangoproject.com/ticket/27234#comment:7>
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/067.6908aaaa2e9ed03a3a04f9f5d00ef126%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
