#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 Ben Whale):
Agreed, and even if it was possible it'd be along way off. The additional
work required for beginners to get up and running would also need to be
considered.
It might be possible to replace the calls to django.server with calls to
django.request without removing {{{runserver}}} or do you think
django.server is too tightly integrated? Such a change might make it
easier to remove {{{runserver}}} in the future?
As a side point, would you be against including a comment in the django
logging documentation that certain kinds of logging (e.g. all incoming
requests) are better handled by the actual webserver (e.g. Apache or
Nginx) in a production or remote development environment?
--
Ticket URL: <https://code.djangoproject.com/ticket/27234#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 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/067.23a77d14781567f24b40052f4f662bb9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
