On 2 Lip, 22:49, Paul McGuire <pt...@austin.rr.com> wrote: > > Does anyone have any clue what that might be? > > Why the problem is onGAE(even when run locally), when command line > > run works just fine (even withrecursionlimitdecreased)? > > Can't explain why you see different behavior onGAEvs. local, but it > is unusual for a "small" translator to flirt withrecursionlimit. I > don't usually see parsers come close to this with fewer than 40 or 50 > sub-expressions. You may have some left-recursiongoing on. Can you > post your translator somewhere, perhaps on pastebin, or on the > pyparsing wiki Discussion page (pyparsing.wikispaces.com)? > > -- Paul
@David, thanks for the advice, I did ask on GAE list, id not get answer till now though. @Paul, I think I solved it. I did extensive test during weekend and it appears that my regular translator almost reaches 1000 recursion limit. Probably the last time I've tried to increase the recursion limit for GAE app I did it in the wrong place. (For future, if you'd like to do it, the best and working is to set that right before call to run_wsgi_app(application)). The only think that remains is, I need to review the grammar and how processing happens that I reach that limit with GAE. Thanks guys, Soltys -- http://mail.python.org/mailman/listinfo/python-list