Re: moving from Django 1.6 and south to Django 1.8 -- auth migrations not applied

igration for that app and change > EmailField max_length to 75 since that matches your schema. Then you can > auto-generate a second migration to update the max_length to 254. > > On Tuesday, April 21, 2015 at 11:42:45 AM UTC-4, Scott Hostovich wrote: >> >> I'm using a

Re: moving from Django 1.6 and south to Django 1.8 -- auth migrations not applied

), On Monday, April 20, 2015 at 4:19:56 PM UTC-4, Scott Hostovich wrote: > > I moving from Django 1.6 and south to Django 1.8. I followed the > instructions at > https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south > and things seemed to work fine. Then

upgrading from Django 1.6 and south to Django 1.8

I'm upgrading from Django 1.6 and south to Django 1.8. Following the instructions at: https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south seems to work initially but then realize that the user model wasn't updated: https://github.com/django/django/tree/1.8/django/co

moving from Django 1.6 and south to Django 1.8 -- auth migrations not applied

I moving from Django 1.6 and south to Django 1.8. I followed the instructions at https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south and things seemed to work fine. Then I noticed that the auth migrations did not get applied to the database (https://github.com/django