Actually, I do not want tg.request. I juste want to be able to use/translate strings based on LazyString. The fact that we need a tg.request context is not right: some of our problems are related to daemons sending emails. There may be no tg.request context at all. The other usecase is an HTTP context but in another server (cherrypy+wsgidav - no turbogears on front layers - only shared libraries based on our tg-related code)
When trying to use "/_test_vars" (which is quite ugly in a production environment) we got errors on SQLAlchemy transactions (the commit was already done when we were trying to commit some stuff). I agree with you about creating a tg application context, but a tg application context is not a tg.request context (the application exists without a user request, does'nt it ?) Damien -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/turbogears. For more options, visit https://groups.google.com/d/optout.
