omab/django-social-auth — pull request #370 by estebistec (2012-06-15 03:27:17+00:00)
Title: Load social_auth models based on a configuration setting

I opened this pull request early to request feedback as I work on it. I see pull 297 [1], where the author wants to make SocialAuthUser optional. I actually want the ability to replace the storage for all models entirely. If I'm building an app on top of, e.g., mongodb, I'd rather not have to have an SQL database just for users/social-auth.

My plan is:
1. implement configurable storage specification, defaulting to current django models (done in the current commit)
2. build an alternate storage module that works, recording the required protocol for such modules along the way (this is my next step, unless you veto the effort).

So, hopefully that gives you a good idea of my goals here. I'll try to keep my commit comments descriptive.

[1] https://github.com/omab/django-social-auth/pull/297