On Nov 13, 2011, at 7:45 PM, howesc wrote: > ok, i did a little digging and this is quickly out of my current realm of > understanding. > > it seems that the older SDK > (http://code.google.com/p/googleappengine/downloads/detail?name=GoogleAppEngineLauncher-1.5.5.dmg&can=1&q=python+os+x) > has custom_import re-run on each request, but the new version of the SDK > custom_import is not re-run. so the best i can make sense of is that GAE is > now caching things, but only parts of the environment? (i could be > completely wrong in my analysis as i don't fully understand how web2py sets > up the environment, execs code, does imports and caches). all i can say with > certainty is that GAE changed something in this SDK version that causes > web2py imports to break. > > any thoughts on how i can better debug this? other notes: i'm running on OS > X, and using python2.5 (cause i'm not ready to test and roll-out python 2.7 > to my clients quite yet)
That's interesting. I got a similar impression from reading the GAE docs. There's a suggestion that even though the requests are nominally served through the CGI mechanism, the overhead of running the whole thing from scratch on every request is avoided. Just how they do that is a mystery to me, and since I've been using 2.7 & WSGI, I haven't played with it. I suggest some logging to see just what gets run on each request.
