Hi Lythoner,

> Yes. I have modified sqlalchemy_driver.py file to use SqlAlchemy 0.4.

Actually what I meant was that there is already an SQLAlchemy 0.4 driver 
in there:
http://authkit.org/trac/browser/AuthKit/trunk/authkit/users/sqlalchemy_04_driver.py

It uses some experimental middleware I wrote to wrap some of the 
SQLAlchemy functionality in WSGI middleware - this isn't the recommended 
approach in Pylons though so you might prefer to use your driver instead.

> Do 
> you have the unit tests for sqlalchemy_driver?. Please spot me the 
> location, I would give a try. 

Yes try here:
http://authkit.org/trac/browser/AuthKit/trunk/test

You run them using nose. I think the command is:
nose test/test.py

If Trac is temperamental when following the above links just press 
refresh a few times and it should work.

> I am newbie to pylons, sqlalchemy, have  
> little programming experience in Python itself. Whatever I have done MAY 
> NOT be correct.  I have attached the modified file, which I haven't 
> given much review. If you give me some comments/suggestions, I love to 
> do this migration.

Thanks for the offer, do you want to take a look at the existing version 
and see if it meets your needs first? The version I've linked above uses 
a new experimental version of the API which creates a new Users instance 
each time it is called. The methods each have access to the WSGI environ 
  so in principle the new API should be a lot more flexible than the old 
one.

We could add your version in too if you are confident it will end up stable?

> Sorry, It was SessionContext not SAContext.

Ahh, makes more sense.

Cheers,

James


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" 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/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to