On 4/5/06, Max Ischenko <[EMAIL PROTECTED]> 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).
With my "less-simple" suggestion, the addition would produce a new lazystring that you can still call str() or unicode() on outside of the context of a request and get the right value out. > > > Of course, the simplest solution is to implement __add__ such > > that the lazystring is evaluated and concatenated. > > +1. This seems pretty trivial to do (do you mind opening a ticket?) But, I think the other solution is ultimately better. The more we delay the evaluation of the string, the better. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
