Andrew Lentvorski wrote: > James G. Sack (jim) wrote: >> Just finished a first look and play session with winpdb >> http://www.digitalpeers.com/pythondebugger/ >> >> .. Looks very nice to me. Wonder why[1] I hadn't run into it before? >> >> If for nothing else, the namespace (variables) browser is worth it's >> weight in gold .. allows poking into all those mysterious objects. 8-) > > You might want to check out "ipython" as well: > http://ipython.scipy.org/ > > It makes using python work very much like Mathematica. It has > input/output history. You can also use <tab> to do autocompletion of > objects as well as introspection.
I _have_ used and liked ipython, for the benefit of history, tab completion, missing-paren forgiveness in things like 'dir <thing>' and for its pretty-print formatting. I gather from a quick look at the site you posted, that there are additional components and uses I didn't know about, that (eg) get into debugging. Still, the winpdb gui fits my particular preferences for introspection very nicely. Being able to step around the call-stack and see the locals (and the code) seems especially neat. The breakpoint capabilities and exception diagnosing seem to work in a pretty intuitive way, too. It doesn't step through binary libraries, of course. But it does BTW, winpdb's client-server model admits remote debugging. And there is a text-only rpdb2 tool. They also make some _claims_ about correct thread handling, and superior performance .. can't confirm those. Another feature of possible interest to some is that it uses wxPython, and runs in Microsoft Windows. Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
