On Dec 19, 2007 6:47 AM, David Danier <[EMAIL PROTECTED]> wrote: > True, but having to duplicate every app in django.contrib I want to use > (and which uses django.contrib.auth.models.User) only because the > ForeignKey is wrong, that's bad in my opinion. And fixing the admin will > not really help with this issue. So I think it would be nicer to really > fix the problem in django.contrib.auth, not django.contrib.admin.
OK, so what you want is very very different from what I'm getting at here. What I want == newforms-admin can be run without django.contrib.auth, and people who do so understand that in doing so they are jettisoning anything which relies on django.contrib.auth. What you want == django.contrib.auth becomes a magical wrapper which transparently switches out the entire auth codebase on demand so that 'from django.contrib.auth.models import User' might do practically anything depending on the configuration. These are so very much unlike each other that I'm not even sure why one came up in a discussion of the other. Perhaps I'm missing something? -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
