of the admin app, and
> that's usually the answer that is given.
>
> Would including a built-in contrib app that implements access control
> lists be outside the scope of Django?
>
> I figure a design similar to the current admin site will be needed to
> create a generic
2009/1/7 Malcolm Tredinnick :
>
> I'm also thinking that requiring evidence of people walking across hot
> coals in order to use an application is probably a good pre-requisite
> for inclusion in django.contrib.
>
+1
The gmail ads are conveniently offering me 'Firewalk Teacher Training'
and 'Find
On Wed, 2009-01-07 at 12:57 -0700, Jeff Anderson wrote:
> One of the most requested features/howtos/how-comes/why-nots that show
> up on the Django users list is Access Control Lists, or row-level
> permissions. Almost always, the question is about how to get the admin
> app to use them. This is o
s outside of the scope of the admin app, and
> that's usually the answer that is given.
>
> Would including a built-in contrib app that implements access control
> lists be outside the scope of Django?
>
> I figure a design similar to the current admin site will be needed to
&
y the answer that is given.
Would including a built-in contrib app that implements access control
lists be outside the scope of Django?
I figure a design similar to the current admin site will be needed to
create a generic ACL subsystem. An access list would be defined for each
app, similar to how an
