Hi Benoit, Like I said in my last response, I'm *not* seeing the problem. Saying "I'm seeing the problem" doesn't help me. Saying "I've got a custom User" doesn't help me either -- I've got a custom User (several, actually - a test case extending AbstractUser and one extending AbstractBaseUser, plus a of live projects using custom user models), and dumpdata is working fine for me on all of them.
What I need is a complete project that demonstrates the problem -- the minimal set of instructions necessary to reproduce the problem you are seeing. I also need you to tell me what version of trunk you're using. Django 1.5 hasn't been released yet, so the problem is with a specific revision, not with a final release, and since the branch is under constant development, the *exact* revision matters. Yours, Russ Magee %-) On Fri, Nov 23, 2012 at 5:33 PM, Benoit Petit <benoit.petit.i...@gmail.com>wrote: > I have the same issue with django 1.5. I have a custom User model that > extends AbstractUser. > > Regards > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-developers/-/VFhbHqt6P4cJ. > > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
