Russell, my reply there isn't meant to be confrontational and yet re-reading it I can see it being easily interpreted as such. My intention is to ask whether there is something about swappable that I am missing. It seems to work the way I stated above but your statement seems to imply that their is some missing piece that needs extra mechanisms surrounding model loading. So, am I missing something?
Marc, Thank you for your reply, and I respect the difference of opinion. If I understand you correctly, you feel that this belongs in a separate contrib application because to refactor auth to be generic enough to handle both the built in User and EmailUser will involve too much magic. I'm curious if you've taken a look at the code behind django-authtools. I feel that it is a good example of what some of the changes to auth.forms or auth.views might look like, and that there is less 'magic' involved than you might think. -- 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.
