When Wing is used to debug a Python program remotely, the Wing debugger core must be installed on the remote machine. The easiest way to do that is just to install Wing IDE there. If that is not possible, there are two options: (1) Copy just the debugger files from a Wing IDE installation on the same type of machine, or (2) compile the debugger core from sources (available for Wing IDE Professional only).
Copying from Wing IDE Installation
When copying from an existing Wing IDE installation on another machine, you will need to copy all of the following files and directories under WINGHOME, which is the Wing IDE installation directory or on OS X the Contents/MacOS directory within the .app folder:
wingdbstub.py bin/wingdb.py bin/#.#/src/debug/tserver bin/#.#/src.zip/debug/tserver (only Python 2.5) bin/#.#/opensource/schannel (Python versions other than 2.5) bin/#.#/opensource.zip/schannel (only Python 2.5)
Replace #.# with each version Python you wish to debug under (for example, 2.5). You can omit the directories for the versions that you are not using.
The directories within zip files (used only in Python 2.5 and later) can either be copied by moving the entire zip file or by creating a subset that contains only the necessary directories.
Be sure to copy these directories from a Wing installation on the same type of host, so that on Linux/Unix you include *.so extension modules, on Windows *.pyd extension modules, and so forth.
Compiling from Source
On machines for which there is no Wing IDE installer, the debugger core can be installed from source code. This is only available to Wing IDE Professional customers, and requires signing a non-disclosure agreement. The compilation instructions are located in build-files/README.DBG-SRC/txt in the source distribution that you will be provided with.
|« 13.1.1. Remote Debugging Example||Table of Contents||13.2. Attaching and Detaching »|