#27234: django.request receives a socket object rather than a request object in
logging
-------------------------------------+-------------------------------------
Reporter: ben-whale | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 1.10
Severity: Normal | Resolution: invalid
Keywords: django.request | Triage Stage:
runserver WSGIRequest socket | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by ben-whale):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
Bug #27233 has been resolved as invalid. This indicates that it is invalid
to use the ServerFormatter in anything other than the django.server
logger. As a consequence the {{{socket}}} vs {{{WSGIRequest}}} issue is
partly (fully?) resolved.
The reason for the difference in the {{{request}}} object comes from calls
being logged by django.request and django.server through the same
formatter. So no surprise when different arguments result.
I'm guessing this should be marked as invalid since the implementation of
the ServerFormatter is an internal detail and the user should never see
the difference mentioned above.
--
Ticket URL: <https://code.djangoproject.com/ticket/27234#comment:1>
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.dc533f73b2b7e22683d0a56caf7c6315%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
