Hi, Joseph and I had a discussion today about how to work our two projects together. Here is what we decided upon.
Because Joseph is currently implementing default_has_permission by using user.has_perm. I will be adding row level permissions to the user.has_perm method. To allow for this, user.has_perm will be given an optional "object" attribute that will by default be set to None. If the object is specified and row level permissions are enabled for that object, row level permissions will be checked. In the end, this won't break any functionality for developers using user.has_perm. In the cases where developers want to utilize row level permissions, it is probably best to rewrite the user.has_perm to be the has_permission method Joseph has created. Please feel to comment or ask questions. I'll be rolling out the updated code this weekend, and maybe middle to late next week, Joseph and I can merge branches to make sure that testing is done with the systems integrated rather then find out at the end that there are bugs. Thanks, Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
