nkeric wrote:

>btw, how about creating a more generic patch for django's generic view
>methods? Since this is really a "generic" scenario - I usually need to
>"get some object list by some condition" :)
>  
>
Actually I asked on django-dev if this thing would be of any interest if 
I implement it (the implementation is quite simple really). But the idea 
didn't receive any support.

In fact there are many things that can be added to generic views that 
require some simple wrappers now (making them @login_required is one 
example). This is the question of where you stop adding functionality to 
generic views. On one end there is a solution so basic that it is not 
useful to anyone and on the other end there is a solution so bloated 
that nobody event wants to start to learn how to use it :-). I think we 
should entirely trust core devs in choosing what is right here since 
they're already made Django that looks so balanced in what it can do 
automatically and what it required to do by hand.

However I, personaly,  think that filtered object_list is so common case 
that it really should be generic.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to