On Wed, May 21, 2008 at 3:00 PM, Jeremy Bornstein <[EMAIL PROTECTED]> wrote: > (assuming your profile model is called "UserProfile")
I think you just answered your own question. Consider a third-party app that might be used to manage user profiles, but leaves the actual implementation of that profile to each individual project. There's no way it could possibly know what you've named your user profile model. By including a setting to specify this, and a standard method to handle the retrieval behind the scenes, it becomes a quite reasonable scenario. I could be wrong about the actual reason it was implemented like that, since I wasn't involved in that process, but that's at least one big advantage for doing it the way it's done. -Gul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
