On Thu, Mar 31, 2011 at 1:30 AM, Andrey Zubko <[email protected]> wrote: > I'm interested in participating in your mentors program in Google > Summer Code. > Clearly looking on the current situation with authentication, > authorisation, customization of users, I could say that there is no > simple solution for achieving all possible modifications of user auth > subsystem. I would like to propose such approach : > contrib.auth.models.user should be a proxy class for real User-model > class that will be defined by developer. By proxing we simplify the > task of importing real-User model, because everywhere we are importing > only contrib.auth.models.User class. > The code for proxying should be looked like : ... > By using properties in this example we are able to emulate classic > User-model. > Developer should be able to specify alternative User model class by > specifying it in settings.py. > For emulating first_name and other fields of User custom model > developer should use property() for hiding.
... and this is the exact model that has been proposed, and rejected in #3011 (albeit with a more complex dance around default values). It also strikes me that if this is your proposal, you've already finished the implementation. Which means this isn't really a "summer of code", as a "couple of hours of code". There's a reason that Django hasn't got a configurable user model. As the wiki page for this project states -- this isn't a simple problem. I've just reinforced this point on the wiki. If you're interested in this project, I suggest you take a look at the discussion about Lazy Foreign Keys -- I've just added a link to the GSoC wiki. This dovetails into a broader discussion about the App Refactor (a GSoC project last year that still needs to be landed to trunk), and app configuration. auth.User configuration is just the most prominent example of a much bigger problem; If your proposal doesn't address the broader problem, it's not going to be taken very seriously. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
