Re: Do I need django.contrib.auth in my INSTALLED_APP when if I don't use the models from there?

Thanks :) Luke Seelenbinder wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > No, you would not. Hope that helps. > > Luke > > luke.seelenbin...@gmail.com > > "I [may] disapprove of what you say, but I will defend to the death your > right to say it." -- Voltaire > > > Vasil Vangelovsk

Re: Do I need django.contrib.auth in my INSTALLED_APP when if I don't use the models from there?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 No, you would not. Hope that helps. Luke luke.seelenbin...@gmail.com "I [may] disapprove of what you say, but I will defend to the death your right to say it." -- Voltaire Vasil Vangelovski wrote: > It's like this: > I actually have 3 projects. T

Re: Do I need django.contrib.auth in my INSTALLED_APP when if I don't use the models from there?

It's like this: I actually have 3 projects. These projects share apps. So all the apps besides the third party ones are placed in one folder which is on PYTHONPATH. The third party ones are in another folder on the PYTHONPATH. Yes 2 of these projects use the admin and do use the ModelBackend f

Re: Do I need django.contrib.auth in my INSTALLED_APP when if I don't use the models from there?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vasil, That will vary on what the apps you are using. If none of the apps depend on django.contrib.auth, you won't need it, unless you want to use the django admin (which depends on django.contrib.auth). To fully answer your question, we would need

Do I need django.contrib.auth in my INSTALLED_APP when if I don't use the models from there?

I'm making a very small project that will use the apps/models from a larger one. This will be hosted on a separate domain. Now the larger project uses the models from django.contrib.auth, but I don't need and don't want to store users in a database for this smaller one. I'll just provide my ow