Oh - sorry, I thought Fran had named it already.
A butterfly issue: our CRUD update/create calls use to put T()'d messages into session.flash. When web2py tries to restore such sessions, this fails silently and creates a new session, which appears to the user as a sudden logout. The issue is that somewhere during restore of the session a statement tries to access T as attribute of a lazyT object. Since the changes of 2233 this happens through the new __getattr__ in lazyT, which in turn calls __str__ which again accesses T through __getattr__ which in turn calls __str__ which again accesses T ...running into an infinite recursion that finally raises an exception. The suggested fix makes the m, s and T class variables, so __getattr__ would not be used to access them, and the whole issue vanishes. Dominic On 2 Sep, 06:06, mdipierro <mdipie...@cs.depaul.edu> wrote: > I was not ware of this. Not sure this is quite the same problem and I > do not understand the proposed fix. > > On Sep 1, 5:59 pm, Dominic <dominic.koe...@googlemail.com> wrote: > > > > > We had an issue with that change in lazyT, > > seehttp://eden.sahanafoundation.org/ticket/621 > > > I wonder ifhttp://bazaar.launchpad.net/~mdipierro/web2py/devel/revision/2242 > > fixes the problem, and if yes - wouldn't the patch as suggested in the > > ticket not have been easier (and cleaner)? > > > Best regards, > > Dominic- Dölj citerad text - > > - Visa citerad text -
