Running pdb.set_trace() from inside a script launched from the Blender
console window issues a message about a missing stdin.
It *is* possible to run pdb.set_trace() as follows, but when invoked
the debugger has no access to sources:
- Open a console window.
- Launch Blender from the console window.
- Run the script from the text editor window, not the console.
Some possibilities come to mind:
1. Study the Jaworski book. Did that. Not helpful unless I want to
use Eclipse. The point is that
I want Leo to be good enough.
2. Modify pdb.py in blender/2.59/python/lib
3. Use winpdb: http://winpdb.org/docs/blender/ and especially
http://winpdb.org/docs/embedded-debugging/
winpdb typically uses wxPython, but the remote debugging option could
probably be built into Leo. The idea is to launch Leo from a console
(I already always do that) and use that console for interaction with
winpdb.
My preference would be to get pdb working with the console. For me,
it's the most natural way. However, it likely depends on a bridge
between the console and pdb, and (sigh) such bridges may not be
possible because basically everything in Blender is C code...BTW,
googling "pdb blender" has turned up nothing useful...
If "plain" pdb seems infeasible, I'll look into winpdb.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
