Hi All, I'm in the middle of trying to understand how a 3rd party python module and utility works (ref <https://github.com/maphew/shortcutter>). The complications surpass my fledging debugging approach of liberally sprinkling print() statements everywhere, so I figured I'd buckle down and learn how to use a debugger properly like the Smart Kids Do. I hit a road block pretty quickly though: the "Debugging with Leo" chapter in the docs are out of step with outside world. One of the first things to do is grab *winpdb*, but that tool/project appears to be in a state of flux. The original project is unmaintained. It's been picked anew as *winpdb reborn*, but is currently straddling the divide of python 2 vs 3.
Winpdb Reborn: https://github.com/bluebird75/winpdb Getting back to Leo debugging: the g.trace and g.pdb sections don't apply to my challenge (I think) because I'm not running Leo scripts, but trying to follow the program execution of the external code. Any suggestions of how I could get started? Thanks! Matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/c8420f39-68f9-4136-9575-515a029044ae%40googlegroups.com.
