There is additional option. If you are using some remote API command shell implementation (e.g. app-engine-patch and Django-nonrel have such) you may mix remote calls with debugging of local code. This is achieving by calling remote shell script under some Python debugger
My choice - install winpdb - really cool though minimalistic. then winpdb <command to run your remote shell> (for app engine patch: winpdb ./manage.py shell --remote) then, winpdb window will be raised, and you may set some breakpoints in local code then continue execution. After continue, you'll be dropped into a remote shell then you should do required imports and call some functions manually to trigger places with breakpoints. (Note, that you may need to place some additional __init__.py files in some root directories of your project, to do import src.foo.bar rather than import foo.bar to force a debugger to get clue where your sources are) On Mar 1, 7:44 am, Calvin <[email protected]> wrote: > The simplest way to debug a GAE app is to just use tons of logging > calls:http://docs.python.org/library/logging.html > > These will show up in the logs area of your app's dashboard. > > If you are running a local dev_appserver.py you can use an IDE like PyDev to > set up breakpoints and watch variables. It's not too hard to set up and > will save you lots of time in the long run. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
