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. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-disc...@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
