On 2/7/07, Patrick Lewis <[EMAIL PROTECTED]> wrote:
>
> On Feb 7, 12:54 pm, "percious" <[EMAIL PROTECTED]> wrote:
> >
> > class testUser(unittest.TestCase):
> > def testGetPassword(self):
> > user = User('user_name', '[EMAIL PROTECTED]', 'the user',
> > 'asdf')
> > print user.password
> > session.save(user)
> > session.flush()
> > session.delete(user)
> > session.flush()
> >
> > OK, so when you print the password you should get some jibberish SHA
> > string, but instead you get a hearty 'asdf'
>
> If you are running TG <= 1.0.1, I think that's a bug with the
> implementation outside of a request for sqlalchemy. Try setting the
> sqlobject config 'identity.soprovider.encryption_algorithm': 'sha1',
> and see if that fools it into working.
>
not sure about this part.
> In svn, it looks like this bug has been corrected, although it looks
> to me like it will raise an exception outside of a running identity
> provider (i.e. in your test case).
>
but yes that is the case your user instances are never being process
by the Identity code, remember that the User class is just a plain
object.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" 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/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
