> > Well, that is the reason why I passed request._current_obj() as > argument to the generator in my code sample. > It solves the issue of being able to access the request and identity. > Ahh.. I didn't even notice that reference.. Unfortunately in my case, I am not referencing the tg.request directly in the generator, but in some library routines that have no idea they are part of it so passing a direct reference to the request object would not work without extensive rewriting (if even possible)
> Other issues are related to the fact that you have to remove, flush > and commit the DBSession yourself. > Good to know.. so I guess each layer in WSGI stack really needs to take special care of generator returns when they have post-request processing and handle those cases. -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To view this discussion on the web visit https://groups.google.com/d/msg/turbogears/-/SMFFm_ORxxIJ. 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.
