Breakpoint didn't work when debugging GAE SDK 1.7.6

Apr 3, 2013 at 1:40 PM
Python Tools ver 2.0 beta
VS2012
GAE 1.7.6
WIN7 32BIT
Python 2.7.3

Breakpoint didn't work both on attach-to-process method and start-from-vs method.
I don't know howto debug GAE programs now. Help me!
May 12, 2013 at 10:19 PM
Edited May 12, 2013 at 10:22 PM
I also can't get this working
Python 2.7.4 32-bit
VS2010 + PTVS 1.5
GAE SDK 1.8
Project Startup File: C:\Program Files (x86)\Google\google_appengine\dev_appserver.py

when debugging it runs fine, the test webpage runs fine, breakpoints just dont work
May 12, 2013 at 10:49 PM
Edited May 12, 2013 at 11:17 PM
So I guess ever since GAE SDK 1.7.6 breakpoints haven't worked for any python debuggers because dev_appserver.py spawns another process or something

Using old_dev_appserver.py (instead of the new dev_appserver.py) works with breakpoints, and its the solutions I'm using

Here are some links tracking this issue
http://stackoverflow.com/questions/16149813/unable-to-debug-dev-appserver-in-google-app-engine
http://stackoverflow.com/questions/15514743/pydev-breakpoints-in-app-engine-1-7-6-broken

basically,
The reason why PDB doesn't work is because dev_appserver is using stdin/stdout for interprocess communication. Python has built-in libraries for IPC: http://docs.python.org/2/library/ipc.html. dev_appserver should use these, and then stdin/stdout can be left alone so that PDB still works
May 12, 2013 at 11:10 PM
Perhaps someone more knowledgeable in Python debugging in PTVS can figure out how to implement these instructions on how to debug the new dev_appserver.py :

https://docs.google.com/a/london.org.il/document/d/1CCSaRiIWCLgbD3OwmuKsRoHHDfBffbROWyVWWL0ZXN4/edit
Coordinator
May 13, 2013 at 8:30 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Coordinator
May 13, 2013 at 8:32 PM
I've created a work item for this, but it's not in our schedule and we're unlikely to get to it.

If anyone else wants to do this though, we're happy to accept contributions. It looks like this would require a special script that loads our debugger - currently our launcher starts the debugger and loads the script, which is the wrong way around for GAE.