#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):
No, I don't think the PR you mentioned has an effect on this.
From the documentation:
`django.request`: "Log messages related to the handling of requests."
`django.server`: Log messages related to the handling of requests received
by the server invoked by the `runserver` command.
If that distinction isn't clear, then I guess the documentation should be
clarified. Perhaps it was all less confusing before `runserver` was
modified to use logging (#25684).
My ideal scenario involves deprecating `runserver` in favor of a normal
wsgi runserver such as gunicorn (#21978) so that Django doesn't need to
maintain it's own minimal server, but it's unclear if it's feasible.
--
Ticket URL: <https://code.djangoproject.com/ticket/27234#comment:5>
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.5754abfc140f26ab62ca4cb629641271%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
