On Tue, 2009-02-10 at 21:51:17 +0100, Gustavo Narea wrote: > Hello, everybody. > > I'm pleased to announce that I have: > 1.- Finished the guide on how to use repoze.what in Pylons: > http://wiki.pylonshq.com/display/pylonscookbook/Authorization+with+repoze.what > 2.- Created a plugin to integrate repoze.what in Pylons applications: > http://code.gustavonarea.net/repoze.what-pylons/ > > So hopefully now using repoze.what in Pylons-based applications will be much > easier. :)
I really appreciate the documentation you're providing. Had to deal with repoze.what in the beginning of January and liked it a lot, but having these resources would have been even more helpful. :-) Having said that, there's one issue I've encountered while integrating repoze.what: model.meta.Session was imported in config/middleware.py at the time when model.init_model() hasn't been called yet, so Session was still None and stayed as that in the scope of middleware.py even after init_model() initialization. As a workaround I've modified Session init code according to example at <http://pylonshq.com/pasties/1046>, but now I see that it's enough to import Session *after* load_environment() call in middleware.py. This still seems to be relevant to your guide (though I haven't tried it from scratch), and the cure should be the same: import add_auth after the line where load_environment() is called. -- Audrius Kažukauskas
pgpu7xVRcOBFW.pgp
Description: PGP signature
