#15179: django.test.client.Client.login fake HttpRequest is not run through middlewares -----------------------------------+------------------------------------ Reporter: Ciantic | Owner: akaariai Type: Bug | Status: new Component: Testing framework | Version: master Severity: Release blocker | Resolution: Keywords: | Triage Stage: Accepted Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -----------------------------------+------------------------------------ Changes (by timo):
* needs_better_patch: 1 => 0 * has_patch: 1 => 0 * severity: Normal => Release blocker * stage: Ready for checkin => Accepted Comment: Seems like it could be a legitimate concern, although I'm not sure how often it will be a problem in practice. It wasn't initially clear to me where the "real response" was generated; I believe that refers to the logic in the `self.request()` calls that were added. Marking as a release blocker so we make a decision before the 1.7 release. -- Ticket URL: <https://code.djangoproject.com/ticket/15179#comment:31> 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/065.e2a5faa49c1fc72f0b67e90103a7bae7%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.