On Wednesday, September 18, 2013 6:59:17 PM UTC-6, Russell Keith-Magee wrote: > > > On Thu, Sep 19, 2013 at 8:37 AM, Aaron Merriam > <aaronm...@gmail.com<javascript:> > > wrote: > >> Luke, I'm +1 on wanting a solution that allows "just set AUTH_USER_MODEL >> to 'auth.EmailUser', and done". >> >> It'd be nice if 'swappable' could accomplish this for us. Something >> along the lines of for any set of swappable models which are swappable for >> the same settings value, only load the one that is named by the settings >> value. I am taking some time to read the source surrounding this setting >> and model loading to even figure out if this is a possible modification. >> Russel, curious about your thoughts on if this approach would be something >> you would sign off on. >> > > Can't say I'm wild about it. Explicit is better that implicit. >
I think I might be missing something salient. How do these solutions vary regarding explicit vs. implicit? I guess I don't see why that particular line is germane. > If we were going to go down the "single setting" model, I'd rather see it > as "you put auth_email in your INSTALLED_APPS, and that automatically sets > AUTH_USER_MODEL". However, that requires infrastructure that we don't have > at the moment. See my permanent refrain to App Refactor :-) And even then, > I'm not necessarily convinced it's the right way to go. I don't see 2 > explicit settings to be especially onerous, or difficult to explain. One > setting installs the app. The other tells Django which model in that app to > use. They really are separate concerns. > Are they? I guess I see the User model to be used as a setting within auth... Best Regards, Luke > -- 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.
