Hi Chris, You've asked if anyone has had success, which implies the thou haven't, but you haven't said what problem you're having.
My experience (which is logged in the ticket you reference) is that yes, running convert_to_south raises an error -- but the migration is created correctly, and works fine if you try to use it. So until the bug is fixed, you just have to hold your nose when the error is raised, and continue on as normal. If you're having a different problem, then we'd need to see details (and you'll likely get better responses on the South mailing list). Yours, Russ Magee %-) On Wed, Nov 21, 2012 at 12:16 AM, Chris Pagnutti <chris.pagnu...@gmail.com>wrote: > I'm wondering if anyone has ever had success with using South when you > have AUTH_USER_MODEL set to a custom User model. I've made various > attempts, which are basically all the same steps but in different orders. > Basically, my problems is related to this ticket > > http://south.aeracode.org/ticket/1179 > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-users/-/kdlkey4FboEJ. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
