On Jul 13, 1:04 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> defines AUTH_BACKENDS to be a string, not a tuple, and that is the
> error you are catching (note the missing comma). Note the missing
> comma. If you have the comma in the tuple, Django correctly reports
> that the backend doe
On 7/12/07, Mario Gonzalez <[EMAIL PROTECTED]> wrote:
>
> in my settings file I set AUTHENTICATION_BACKENDS = ('something.that-
> doesnot.exists') so when you use the authenticate() method in some
> view a ValueError is raised. So, my patch catch that exception in
> load_backend() method.
>
> I
On 11 jul, 22:33, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
>
> > 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
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
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 p
On 7/11/07, mario__ <[EMAIL PROTECTED]> wrote:
>
>Please take a look at this url http://code.djangoproject.com/ticket/3505
> I wrote a little patch for the ticket subject. Comments or kicks will
> be appreciated :-)
Can you help out a little bit here by providing a test case (not
necessarily
