On 9/10/06, patrickk <[EMAIL PROTECTED]> wrote: > in my view, anything that´s not needed for user-authentication > belongs to a user-profile. for me (and I may be wrong here) a user- > profile is for personal information (like first name, last name, > address and what have you).
As I see it, paring down to "only what's absolutely necessary for authentication" has two big problems: 1. Not everybody will agree on "what's absolutely necessary for authentication"; you may want username/password, someone else may want email address/password, someone else may want an OpenID token... 2. While technically only username/password are "required" for authentication (with the built-in auth backend; let's set aside custom backends for the moment), the email address and first/last name fields are useful enough, and used in enough use cases, that requiring extra work to get them just wouldn't feel right. In other words, I see this as being about providing a baseline of common fields; the fewer people who *have* to define a profile model to get what they need, the better. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
