On Sep 25, 2013, at 2:58 AM, Marc Tamlyn <marc.tam...@gmail.com> wrote:
> Other things which appear to be bugs to me: > - You automatically register an admin class for any custom user model, which > is likely to break validation. > - If I set first_name and last_name as REQUIRED_FIELDS then your admin class > will break validation or render a weird form as the field names appear twice. > > The Admin related issues here are the biggest problem. If admin validation > fails for *any custom user model*, then the server will not start if > contrib.auth is installed. I fixed these. :-) I am by no means claiming that these are the only drawbacks of my approach, but this is a simple fix: only register User or EmailUser. Thanks! L -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
