#27234: django.request receives a socket object rather than a request object in
logging
-------------------------------------+-------------------------------------
     Reporter:  ben-whale            |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Uncategorized        |                  Version:  1.10
     Severity:  Normal               |               Resolution:
     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:  closed => new
 * resolution:  invalid =>


Comment:

 Actually it occurs to me that the documentation should probably be
 altered. For 1.10 it implies that django.server is the same as
 django.request except that it only logs when the {{{runserver}}} command
 is used. This is incorrect as django.server receives sockets rather than
 WSGIRequests it is also incorrect as the {{{record.args}}} is different in
 both cases.

 So either the documentation should be changed or the code should be
 altered to match the documentation?

--
Ticket URL: <https://code.djangoproject.com/ticket/27234#comment:2>
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.b0a003222fe7d66ca1d3188e587e2d3e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to