Thank you guys.
I've been trying to use winpdb without success and would like to ask for some help.
When I run FC I notice in the python console. Python 2.6.2 (r262:71600, Jun 22 2009, 21:41:42) [MSC v.1500 32 bit (Intel)] on win32
The winpdb readme.txt says " Winpdb is compatible with CPython 2.3 or later. Winpdb is NOT
compatible with Jython or IronPython."
I assume that CPython = Python, is that right?
Then I installed winpdb and got:
C:\Python27\winpdb-1.4.8>python setup.py install -f
copying winpdb.py -> build\lib
copying rpdb2.py -> build\lib
copying winpdb_inst.py -> build\scripts-2.6
copying and adjusting winpdb_.pyw -> build\scripts-2.6
copying winpdb.bat -> build\scripts-2.6
copying rpdb2.bat -> build\scripts-2.6
copying build\lib\rpdb2.py -> Lib\site-packages
copying build\lib\winpdb.py -> Lib\site-packages
byte-compiling Lib\site-packages\rpdb2.py to rpdb2.pyc
byte-compiling Lib\site-packages\winpdb.py to winpdb.p
copying build\scripts-2.6\rpdb2.bat -> Scripts
copying build\scripts-2.6\winpdb.bat -> Scripts
copying build\scripts-2.6\winpdb_.pyw -> Scripts
copying build\scripts-2.6\winpdb_inst.py -> Scripts
It seems that it is OK.
To test I tried to debug the FC script importDXF.py, so I copied the line "import rpdb2; rpdb2.start_embedded_debugger(password) " to it. The instructions from http://winpdb.org/docs/embedded-debugging/
says that the script will freeze for a default period of 5 minutes, waiting for a debugger to attach.
When I open a DXF file with FC it works, meaning that it opened the file but winpdb does not froze the script as it should.
What am I missing?