#34781: Clarify documentation of `request` objects in the `django.server`
logging
namespace.
--------------------------------------+------------------------------------
Reporter: Keryn Knight | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Other) | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Natalia Bidart):
* type: Uncategorized => Cleanup/optimization
* component: Documentation => Core (Other)
* easy: 0 => 1
* stage: Unreviewed => Accepted
Comment:
Hello Keryn, thank you for your ticket!
I have reproduced what you described (I preferred to extend the project's
settings to customize the `LOGGING` value instead of changing the source
code, but same result).
The Django code does indeed pass as `extra` logging context what the
`WSGIRequestHandler` is given as `request` by the Python lower level
libraries, so I believe Django can't do anything beyond that. Perhaps a
minor clarification to the docs is worth it.
On that basis, I'm tentatively accepting this report. Would you like to
prepare a patch?
--
Ticket URL: <https://code.djangoproject.com/ticket/34781#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018a03eb4a6d-ae0dce59-2526-4e4e-8309-c8c0bbf7d893-000000%40eu-central-1.amazonses.com.
