GAE with SDK 1.30

[Matt Feifarek]

Has anyone tried the new release of the GAE SDK?

I am basically following Jason's work here:

http://countergram.com/articles/pylons-google-app-engine/

And I can get Pylons to run, but the interactive traceback doesn't work.

First, it seems that one has to change the StatusCodeRedirect() line in middleware.py to include 500 errors, or the middleware doesn't try to eat the traceback.

Second, even when that works, the stylesheet is wrong, and trying to open the debugger console via the [+] button simply returns this message: "The server has either erred or is incapable of performing the requested operation. Debug 1261363666 not found (maybe it has expired, or the server was restarted)"

It seems like the context/request is gone, which makes sense... GAE would probably strip down the environment to be ready for the next request. If indeed "StatusCodeRedirect" does do a redirect, then the request which causes the error is probably long gone.

Does anyone have any way to make this work?

Thanks.

[Ben Bangert]

On Dec 20, 2009, at 6:51 PM, Matt Feifarek wrote:

Has anyone tried the new release of the GAE SDK?

I am basically following Jason's work here:

http://countergram.com/articles/pylons-google-app-engine/

And I can get Pylons to run, but the interactive traceback doesn't work.

The interactive traceback can't work as there's no guarantee the same machine will handle the same request, nor will GAE retain the process between requests with any certainty.

Cheers,

Ben

[Matt Feifarek]

On Sun, Dec 27, 2009 at 5:32 PM, Ben Bangert <b...@groovie.org> wrote:

The interactive traceback can't work as there's no guarantee the same machine will handle the same request, nor will GAE retain the process between requests with any certainty.

Sure, but I'm talking about running on the SDK (the local machine emulator).

I'm cool with not having debugging when deployed (we turn that off in Pylons by default anyway) but I sure would like it back when developing. As is, we get a plain text traceback... without even syntax highlighting.

And of course print statements don't work either, since GAE captures those for output to the stream. So poor-man's debugging is out, too.