Max Ischenko wrote: > > That would make Max's example above > > return a lazystring that will get evaluated during the request. > > Actually, the error occurding while running my unittests - the request > was not detected and thus a lazystring was used. I guess I could mock a > request to simulate real behaviour (and wouldn't ran into the bug > then). >
The request_available function checks the presence of headers into the request object, we can make a more precise check if we try to set/unset an attribute and catch the exception I think. > > Of course, the simplest solution is to implement __add__ such > > that the lazystring is evaluated and concatenated. > > +1. +1, if you want to do that no problem, I'm really not a i18n expert. Ciao Michele --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
