

You can find this path using the Python Console in eclipse:
DEBUG SCRIPT PYTHON HOW TO
First it needs to know where all the PyDev debugging stuff lives, because this will tell Blender how to communicate with Eclipse. Blender, on the other hand, needs a little help. So, Eclipse if fully equipped to do the debugging at its end. The script actually runs in Blender, but the debugging takes place in Eclipse, with Eclipse getting all the necessary information to do this by sending and receiving messages from Blender. When this happens, Eclipse grabs then and does all the debugging by communicating back and forth with Blender. Run/Debug Configuration: Shell Script Last modified: Create: Run Edit Configurations Shell Script Use this dialog to configure running shell scripts.
DEBUG SCRIPT PYTHON CODE
When the Debug Server is started in Eclipse, it sits and listen on port 5678 on the loopback interface for Blender to start sending it messages via the network stack. From what I have read, there are two ways to debug code in Python: With a traditional debugger such as pdb or ipdb. The file you are debugging should be open, with the line it has stopped at highlighted.

I can confirm that this approach (remote debugging plus Python stubs) works well with P圜harm.

append ( PYDEV_SOURCE_DIR ) import pydevd pydevd. PYDEV_SOURCE_DIR = "/usr/lib/eclipse/dropins/pydev/eclipse/plugins/_4.01292234/pysrc" import sys if PYDEV_SOURCE_DIR not in sys.
