I've gone ahead and pushed a new commit to match the spec (not tested yet, 
but hey :D).

On Friday, January 8, 2016 at 3:29:01 PM UTC+1, Florian Apolloner wrote:
>
> Mhm,
>
> I currently see no easy way to give *get_response* access to the list of 
> middlewares like done in 
> https://github.com/django/django/pull/5591/files#diff-dbd7d9159676b15fc9a096b0adb919e9R122
>  
> and following lines. The reason is that providing *get_response* at 
> setup/init time means it has to be one "static" method which is the same 
> for all requests. Aside from using a thread local or stashing the 
> middleware list on the request, this method has no way of getting access to 
> the current middleware chain. Any ideas?
>
> Cheers,
> Florian
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/75b0a8bc-2f6b-46b0-90dd-ae5c9c95156f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to