#25037: Addition to functions http.requests.build_request_repr
-------------------------------+------------------------------------
Reporter: djbaldey | Owner: nobody
Type: New feature | Status: new
Component: HTTP handling | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by djbaldey):
Replying to [comment:3 timgraham]:
> Although it's a common pattern to set `request.user`, I had some
reservations about coupling `HttpRequest` and `contrib.auth` when I first
read this.
>
> Sentry seems to have some way to associate exceptions with users. Maybe
it would be worth looking at how they accomplish that?
This decision does not depend on contrib.auth and request.user. But when
there they - it is of great help to solve the problems of administrators.
--
Ticket URL: <https://code.djangoproject.com/ticket/25037#comment:4>
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/066.87587e46eab218ef8668f09f14d11a61%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
