#15179: django.test.client.Client.login fake HttpRequest is not run through
middlewares
-------------------------------------+-------------------------------------
Reporter: Ciantic | Owner:
Type: Bug | unaizalakain
Component: Testing framework | Status: assigned
Severity: Normal | Version: master
Keywords: | Resolution:
Has patch: 1 | Triage Stage: Accepted
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by loic84):
As mentioned on the PR, I would rename the newly added `response._request`
to `response.request_instance` so it's not confusing that there is a
`response._request` and a `response._request` which are two different
things.
FTR: Ideally the old `response.request` would become a getter with a
deprecation warning that proxies `request_instance.environ`, or be
renamed to `request_data`; however making such property would require a
custom `Response` class which is probably overkill.
--
Ticket URL: <https://code.djangoproject.com/ticket/15179#comment:24>
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/065.e8e41b7226ef9eb9ccc8a8d52fbf6bff%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
