On Fri, Jan 23, 2009 at 2:37 PM, Gustavo Narea <[email protected]> wrote: > > On Friday January 23, 2009 06:21:57 Mark Ramm wrote: >> I actually think this solution isn't quite right. We can do as >> alberto suggests and stop trapping 401's in the error handler, and >> things should go back to working, unless there's another problem I'm >> not seeing. >> >> And we're dropping the sqlalchemy session with the session removal >> middleare, and now repoze.what is outside of that so if it tries to do >> anything on the way out, it won't have an active DBSession. So, the >> current solution is broken. > > Yes, you're right, Mark. I've just fixed this in trunk. > >> What's the related problem you had Gustavo? > > I couldn't use some repoze.who challengers, like the HTTP Auth one. But now it > works because Alberto made the error handler ignore 401's.
I just check my code against trunk and the fix is working for me too, this means we are good to go for b4 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
