id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 6603,QuerySet in extra_context should be handled automatically,Waldemar Kornewald,nobody,"f I pass an 'extra_context' parameter to a generic view I can't use a QuerySet because they'd only be evaluated once (at program start), so the only option is to pass a callable. Unfortunately, this solution increases code size and mental burden on the developer who can pass a QuerySet to 'queryset', but not within 'extra_context', so it's even inconsistent. I'd like to suggest that if a QuerySet is passed to 'extra_context' it should be handled exactly like the 'queryset' parameter: call value._clone(). I've attached a patch that you might use as a starting point. It even reduces the generic views code size by 34 lines, so I hope that alone is convincing enough. ;) (though, I'm not sure if the solution is OK)",,closed,Generic views,dev,,fixed,,,Design decision needed,1,1,1,1,0,0