Hello Uwe,
You can use rpdb2.settrace()
But in fact rpdb2 is not meant to be used like that.
the pdb.set_trace() command belongs to the pdb debugging model, of a
single threaded script that starts the debugger on demand. In
rpdb2/winpdb the debugger works all the time and you break (pause) the
sc
Hello Bryan,
You can restrict the number of variables displayed in the globals
name-space viewer with the filter button located second from the right
on the tool bar.
This will filter out modules, classes, and function names from the
list.
Nir
--
http://mail.python.org/mailman/listinfo/python-li
Thanks for the valuable input. I will look into it.
In the mean time, until I implement your suggestions, here are some
workarounds for the problems you experienced.
1.
In the "Open Source" dialog, instead of typing the full path of the
script you wish to load, try typing just its name (e.g. 'foo
Thanks for the compliments.
I really believe Winpdb is not just another Python debugger, and that
it will be a real step forward in the quality of Python debuggers once
it matures.
Also, don't worry about the .com url, it is a GPL debugger.
Winpdb is still a BETA despite the version number which
