Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6260456 By: fabioz
Unfortunately, I don't know enough of the App Engine to say the actual problem, so, I have to get it, create an account and do an example to know what can be failing there... A common problem in web frameworks (django, turbogears, etc) is that there is usually a 2nd process spawned to run things when your files change, so, for the debugger to work properly you have to run with --no-reload (or some option close to it), or use the remote debugger http://fabioz.com/pydev/manual_adv_remote_debugger.html ), but I'm not sure if that's true for the app engine. The problem with the post vs the bug is that I can forget to answer you (as I won't be able to go on and get an app engine example running here right now). In the report it'd be nice to see the output of the debugger when you run with org.python.pydev.debug/pysrc/pydevd_constants DEBUG_TRACE_LEVEL = 3 DEBUG_TRACE_BREAKPOINTS = 3 Cheers, Fabio ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=293649 ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Pydev-users mailing list Pydev-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pydev-users
