So I should probably get started on the generic-auth and per-object-permissions (hereafter pop) integration soon. I've had problems trying to merge changes from the trunk into the generic-auth branch, so I'd just assume call that branch dead. The actual generic-auth code is just a patch to the trunk [1] The easiest way integrate the two would probably be for me to patch the per-object-permissions branch.
I suppose the other option, for the anal-rentively inclined, (which very often includes me ;) would be to start a new-auth branch, merge the pop changes to it (or even copy the existing pop branch, yeah, ick.), and apply the generic-auth patch to it. This sounds like a total pain in the ass to me. /me grumbles something about his love/hate relationship with svn, specifically merge I am presupposing that gen-auth and pop should be merged together before they get merged to the trunk. If you disagree, let me know. So there's the logistics. Here are the rest of the plans for getting this into the trunk. After the two codebases (gen-auth/pop) are integrated, I plan to refactor out a couple of functions from the django.contrib.models.User.has_perm method in the pop branch. After that, the has_perm method should die. (Some other User methods may suffer a similar fate) I'll put in some backwards compatibility code (that *doesn't* support pop), but I think it should be gone by 1.0. I also want to take a look at how the Meta attributes work for activating this stuff. I'd like to make it a little more generic, but I'll bring it up again after I've taken a look at the code. Thoughts, comments? Joseph [1] http://code.djangoproject.org/attachment/wiki/GenericAuthorization/generic-auth.diff --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
