> Thanks for your answer, Malcolm, > > I was refering to the > branchhttp://code.djangoproject.com/browser/django/branches/per-object-perm... > which (according to the wiki) appeared to be almost ready for > inclusion in the > main branch of 0.96. To me, this always seemed to be the most official > of the > various runs on row-level-permissions.
I am very new to django, I went through the tutorial yesterday and I was looking for some sort of ACLs now. And indeed, per-object- permissions has been mentioned in many threads. A lot of people seemed to be waiting and for a beginner like me, it is quite confusing - so thank you Malcolm for the answer, it is very clear. > > > This is the sort of the thing that will be best done as an external > > third-party project first and then, possibly, proposed as something for > > django.contrib once it has an acceptable user base. > > agreed. however, with the variety of third-party solutions out there, > it is unclear to the uninitiated which one to choose, and which one > works > best with django1.0. wnay recommendation? yes please, if you have any recommendations what worked for you, that would be great It seems to me that lot of developers are opting for auth backend - doing things outside Django. I was looking into phpGACL then I found http://code.google.com/p/spiff-guard/ which is a sort of a similar project in python. I also came across this http://www.djangosnippets.org/snippets/414/ (field level permissions) All the best, --roman --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
