The way you are creating the DB is quite complicated, but I suspect that you are not syncing the base Django applications before doing your magic stuff. That could be the reason why Django is complaining about the auth.User not being installed.
I would do the following: * settings.py with the core apps * syncdb * inspectdb * schemamigration --auto * migrate I strongly feel that your problem has to do with Django processing your models BEFORE doing the base stuff. Can you try this? Regards Leo Leonardo Giordani Author of The Digital Cat <http://lgiordani.github.com> My profile on About.me <http://about.me/leonardo.giordani> - My GitHub page<https://github.com/lgiordani>- My Coderwall profile <https://coderwall.com/lgiordani> 2013/9/19 Lauri Carpenter <lauri.loebel.carpen...@gmail.com> > More information: > > Interactively, I can get a user_model: > > $ python > Python 2.6.6 (r266:84292, Oct 12 2012, 14:23:48) > [GCC 4.4.6 20120305 (Red Hat 4.4.6-4)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> from django.contrib.auth import get_user_model > >>> user_model = get_user_model() > >>> user_model > <class 'django.contrib.auth.models.User'> > >>> > >>> > >>> from django.conf import settings > >>> settings.AUTH_USER_MODEL > 'auth.User' > >>> > > (note that the settings.AUTH_USER_MODEL is being calculated by django, not > set by us; our settings.py file does not include any reference to > AUTH_USER_anything). > > But when this happens during the authentication portion of the web > interface, it causes the traceback, from somewhere within the > django.contrib.auth forms for logging in (see traceback in initial > posting). > > -- lauri > > On Wednesday, September 18, 2013 12:51:30 PM UTC-5, Lauri Carpenter wrote: >> >> We have been using django 1.3.0 for a long time. We are now trying to >> migrate to 1.5.4. We have not changed any schema or model information. We >> have been using two layers of middleware and backends (notably something >> based on SSLAuth Django App to authenticate first by certificate issued >> from a trusted authority, then django_auth_ldap to login via ldap if no >> valid certificate is presented). Both of these live on top of whatever >> user/certificate/client/etc. scheme is supported in django 1.3.0. >> [snip] >> >> -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
