Thanks for the quick low down, very useful! Annoyingly, I need full permission based system on objects, not an owner setup. Objects typically have 5-15 different permissions which may or may not be set, and these need limiting per user per object. Seems like generic-auth was ideal in theory.
Does anyone know why it died? Technical problems, lack of time??? As this is something I would need, it would certainly be sensible for me to look at, and either start again, or try and complete/revive. Also would anyone advise another solution, or would it be fool hardy to try and revive/use it for a project? Mat -----Original Message----- From: django-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of James Bennett Sent: 01 April 2008 21:47 To: django-users@googlegroups.com Subject: Re: Auth System On Tue, Apr 1, 2008 at 3:38 PM, Mat <[EMAIL PROTECTED]> wrote: > I'm looking at django for a new project, and have a quick question, I'm > going to need a mixture of the Query-set branch and generic-auth branch, I > really need object based permissions, but it seems like generic-auth was > last modified ~1 year ago, does that mean its complete, the wiki seems to > say in-progress and docs need updating, does anyone know the state of it? The state of it is "dead". A quick field guide to branches of Django: * queryset-refactor is active and will merge into trunk before Django 1.0 is released. * newforms-admin is active and will merge into trunk before Django 1.0 is released. * gis is active and aims to produce a 'contrib' app which can be bundled with Django at some point. * Branches whose names end in "bugfixes" provide security updates for specific release versions. * Everything else is dead or finished. If the current Django documentation doesn't contain mention of a feature a branch was working on, then that branch/feature never landed. > Also the wiki says "The authentication framework is changing to be far more > flexible, and API changes may be necessary.", what is this likely to be, > Object based permissions??? (I hope!!), and any news on a timeframe? 99.99999999999999999% of what people want "object-based permissions" for is really to implement an admin interface where some users are only allowed to edit things they themselves created in the first place. The refactoring in newforms-admin makes this ludicrously easy to do without a complex permissions system, so odds are that "object-based permissions" are a dead end. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---