On Dec 27, 2007 9:22 AM, kevinski <[EMAIL PROTECTED]> wrote: > This worked great, however shouldn't there be some uniformity in how > the Login_Required argument is applied in all the generic views? This > was not the most obvious solution, and I did not see it anywhere in > the documentation.
Right now, the argument is only available on views which actually create, modify or delete data, which makes sense because those are the ones where, one assumes, authentication is most likely to be needed. As for documenting that you can do this, I could go either way. Personally I think it's one of those "at some point we have to assume that a Django user knows and understands Python" things, because the -- documented -- fact that you can import the actual callables and use them in the URLConf should, to a Python programmer, suggest the possibility that you can do things to those callables before you list them in the URL patterns. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
