On 7/11/07, mario__ <[EMAIL PROTECTED]> wrote: > > On 11 jul, 00:09, "Russell Keith-Magee" <[EMAIL PROTECTED]> > wrote: > > > > Can you help out a little bit here by providing a test case (not > > necessarily a unit test - just a clear set of instructions for how to > > generate they type of error that your patch proposes to catch? I can > > see the general problem that this ticket is working on, but I can't > > see how the patch you provide fixes that problem. > > > > if AUTHENTICATION_BACKENDS is empty or something is wrong then > nothing is detected, only an ImporError. The patch catch the > ValueError.
Where and how is the error revealed? When you import an application? When you syncdb? When you try to authenticate? What constitutes "empty or something is wrong"? I can see what exception you are catching. I just can't see how you would generate that exception, or how it relates to the original ticket description. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
