Amit Upadhyay wrote:
> Have not been following the discussion very closely, but why not have a > parameter use_cache (defaulting to True) in the get_list and making it > completely explicit. Sometimes I like the conveniece of not storing > something in a variable, like from within a template, and calling the > get_list [or get_set or whatever it is called in this branch] multiple times The problem is, there isn't even a 'get_set' in this branch, so there isn't anywhere to specify that parameter. Fetching the data is done implicitly by iterating over the set. In this context, something like a objects.use_cache() method would be more appropriate - it would return a QuerySet with caching. It's then equivalent to the above .all() proposal. Also, we don't want to add a keyword argument to filter(), because they all are used for specifying where clauses. Positional arguments to filter() are used for Q() objects (or will be, once that functionality gets put back in). Luke
