On 1/16/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
Sorry this has taken a while to look at - hopefully I'm not too late
to make a meaningful contribution...
Not a problem. I still haven't finished a patch yet and am certainly
still open to suggestions.
I would make another suggestion - why not keep this in line with
INSTALLED_APPS, and use the last dotted section as the identifying
name; i.e,
AUTHENTICATION_BACKENDS = (
'django.contrib.auth.backedns.ModelBackend',
'mypkg.backends.LDAPBackend'
)
would result in 'ModelBackend' and 'LDAPBackend' being available as
identifying names for backends.
As well as maintaining parity with INSTALLED_APPS, this gets around
Jacob's problem of breakage on update, while breaking full path
dependence.
It fits well with how django currently works, but I don't think that's
how INSTALLED_APPS *should* work. We've discussed named apps before,
and even reached consensus, even though the thread is a year old :D
http://groups.google.com/group/django-developers/tree/browse_frm/thread/7197d27127494ee2/df18ee9b91ba383c?rnum=1&q=app+name&_done=%2Fgroup%2Fdjango-developers%2Fbrowse_frm%2Fthread%2F7197d27127494ee2%3Ftvc%3D1%26q%3Dapp+name%26#doc_df18ee9b91ba383c
IIRC Adrian also posted something to the effect of "let's do that" in
a separate thread within the last few months, although I can't find it
now.
If Adrian and Jacob are still on board for allowing the optional
('path.to.my.app', 'app_name') syntax for an entry in INSTALLED_APPS,
I'll work up a patch that fixes INSTALLED_APPS, and let's
AUTHENTICATION_BACKENDS use the same syntax.
On the other hand, I'm also open to implementing auth backend
configuration exactly as you proposed, and leaving the naming part
until after 1.0. Allowing a tuple in place of a string won't be a
backwards-incompatible change.
Joseph
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
