Nevow (http://www.nevow.com/) uses twisted.cred.
You guys are completely misintrepreting the point of this posting. It
has to do with the auth MODEL. Nothing else. When you say Model, you
are obviously referring to SQL. It is beyond me how you people come up
with LDAP and OpenID and all these other wishes.
If you want to use LDAP or OpenID, you
Okay so I can probably easily do it but I'm too lazy. Also I need to
get the auth module to use our subclass of the User class and not the
original class. I'm honestly not sure how I should do this in such a
way it conforms to Django standard.
And also the Admin and Meta classes.
If you are interested the problem happened when I looked at the
formfields file. I don't know how I would make that custom auth class
friendly...
Writing a patch just requires too much effort. I give up and I'm
reluctantly trying to hack this together now. And it's not even fun
like the website says it is. :-(
I'm not able to write the patch because Django is placing too many
restrictions on what I can do as far as this.
Okay Adrian, I will write a patch. Should I upload it to my site and
send it through here or the bug tracker?
Also I haven't given any thought to the inner Admin class. I'll leave
that as an exercise to the reader, simply because I don't even really
agree with how the inner Admin class is setup.
I was looking at the Removing The Magic wiki page, and it seems you
have no plan to remove the magic from the auth module. This came as
quite a disappointment to me. Many things in the auth module are
magical, and the auth model makes many assumptions.
The auth model can still be easy and fun to
I also suppose you could do something like, in the base class:
_name = None
_password = None
And then in the __init__ function the end user could set _name and
_password, but the get_* functions just seems simpler and more
Django-styled.
11 matches
Mail list logo
