On Jul 26, 6:06 pm, Russell Keith-Magee
wrote:
> One approach that may be worth considering is to look at whether you
> actually need to put contrib.authin INSTALLED APPS. If you're just
> using some of the backend utilities - such as the authentication
> backends - you may not need to sync theau
Yeah, I have thought about removing auth from my installed app but the
problem is I am going to be using the permissions part of the app.
Have the auth app support a custom model would be cool.
Also it might not be to bad to write a custom test runner that will ignore
test from apps listed in a se
On Mon, Jul 27, 2009 at 6:17 AM, Vitaly Babiy wrote:
> Hey,
> I have replaced the default auth backend with my own that requires a field
> to be set on my own custom user objects. So when I run my test suite ( which
> includes the auth app ) most of the auth test fail. Due to the fact that
> djang
Hey,
I have replaced the default auth backend with my own that requires a field
to be set on my own custom user objects. So when I run my test suite ( which
includes the auth app ) most of the auth test fail. Due to the fact that
djangos fixtures don't create user object of my custom type. What is
4 matches
Mail list logo
