Debugging Setup

When debugging Python code running under mod_wsgi, the debug process is initiated from outside of Wing IDE, and must connect to the IDE. This is done with wingdbstub according to the instructions in the Debugging Externally Launched Code section of the manual.

Because of how mod_wsqi sets up the interpreter, be sure to set kEmbedded=1 in your copy of wingdbstub.py and use the debugger API to reset the debugger and connection as follows:

import wingdbstub
if wingdbstub.debugger != None:
   wingdbstub.debugger.StopDebug()
   wingdbstub.debugger.StartDebug()

Note that in some cases you may need to add a short delay between the StopDebug and StartDebug calls, using time.sleep(1).

Then right click on the bug icon in lower left of Wing's window and make sure that Passive Listen is enabled. After that, you should be able to reach breakpoints by loading pages in your browser.

Disabling stdin/stdout Restrictions

In order to debug, may also need to disable the WSGI restrictions on stdin/stdout with the following mod_wsgi configuration directives:

WSGIRestrictStdin Off
WSGIRestrictStdout Off

Related Documents

Wing IDE provides many other options and tools. For more information: