On Tue, Aug 30, 2011 at 2:22 AM, luvspython <srehtva...@gmail.com> wrote: > I can figure out most things, though perhaps very slowly and > painfully, if I can trace through code. I use WingIDE (love it), but > the execution > of the C code is of course hidden, which helped stymie on this > problem. Is there another tool y'all might use and you can suggest > that deals with that problem and would have helped me with this case? > Or is one's ability to figure out this sort of problem largely > dependent on really understanding the system's internals?
In terms of debugging, it's hard to ignore the old favorite stand-by: If In Doubt, Print It Out. Pepper your code with console-output calls and manually trace your code using those. Every other debugging tool you'll ever use is a bonus on top of that; if you accustom yourself to IIDPIO debugging, you'll be able to solve problems in any environment. Python does have a number of other debugging tools, though. I'd recommend looking at pylint, for a start. It's not technically a debugger, but it may be of value. ChrisA -- http://mail.python.org/mailman/listinfo/python-list
