#3011: Allow for extendable auth_user module
------------------------------------+---------------------------------------
Reporter: nowell strite | Owner: dan
Status: assigned | Milestone:
Component: Contrib apps | Version:
Resolution: | Keywords: auth_user
Stage: Accepted | Has_patch: 1
Needs_docs: 1 | Needs_tests: 1
Needs_better_patch: 1 |
------------------------------------+---------------------------------------
Comment (by David Danier <[email protected]>):
Replying to [comment:51 david]:
> What about the new proxy Meta attribute?
I think this may help with some of the problems described here, at least
some of the problems that are avoidable in pure python. Many of these
things can be worked around using the advantages a dynamic language like
python provides, too. For example someone could just import User and then
do somethink like:
{{{
User.my_new_method = lambda self: self.something_i_want_to_do_here
}}}
This may not be as clean as using some proxy-class, but works fine and has
the advantage of not needing to import some "other" user.
As said above I see more fundamental flaws in current contrib.auth. One
might be that you have no clean way to replace AnonymousUser (and put it
into the database for example). Another is the combination of four or five
different applications into contrib.auth (authentication, authorization,
groups, messages, permissions) which goes against everything you try to
teach new django-users when creating applications and makes creation of
new applications for only parts of this more complicated.
There are other tickets adressing some of these issues, see #4604 for
example. You may also notice, that the current patch tries to put a
combination of session and user-based messages into the template context.
This really would not be necessary if you could just choose between two
decoupled message-apps.
@mtredinnick: I'm not sure if restructuring the whole contrib.auth-app
would be appropriate in 1.x anyway, so perhaps this is something that
needs to be done for some 2.x-version. I will perhaps raise this issue on
the mailinglist again, when 1.2 is released.
--
Ticket URL: <http://code.djangoproject.com/ticket/3011#comment:52>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
