[IPython-dev] ipython as a debugger command-line interface?

Rocky Bernstein rocky@gnu....
Tue Mar 10 14:23:08 CDT 2009


This is slightly different that what I was suggesting, but I subscribe to
the Perl notion that "There's more than one way to do it".

If one wants to use ipython as a front end (and I don't see a reason why
not), then the way I'd approach this is to make ipython understand some sort
of common debugging protocol. Otherwise you have  M x N combinations of M
front-ends and N back ends, versus  M+N. (But I realize since this list may
only care about about ipython, it is  N vs. 1.)

Gdb uses the protocol called GDB/MI, but outside of gdb I don't think any
other debugger has adopted it. ActiveState uses
DBGp<http://www.xdebug.org/docs-dbgp.php>,
and not just for their Python IDE and debugger but also I believe for Tcl,
Ruby and Python. And I'm given to believe that there are other Python
debuggers that use DBGp as well. So right now that's what I'm contemplating
in pydbgr <http://code.google.com/p/pydbgr/>.


On Tue, Mar 10, 2009 at 1:49 PM, Ville M. Vainio <vivainio@gmail.com> wrote:

> On Tue, Mar 10, 2009 at 5:18 PM, Rocky Bernstein <rocky@gnu.org> wrote:
>
> > done here. In ruby-debug right now there's a setting to automatically
> enter
> > irb initially; the same could be done in pydbgr to enter python or
> ipython.
> > So maybe what should be done is to add add debugger commands "step",
> "list",
> > "continue" and so on into these invocations of these shells.
> >
> > Thoughts on whether this would be a desirable? Or how easy or difficult
> > would it be to do?
>
> One interesting avenue would be making ipython a frontend for rpdb2 -
> one such frontend is winpdb, and  I don't see why other couldn't be
> ipython.
>
> --
> Ville M. Vainio
> http://tinyurl.com/vainio
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/ipython-dev/attachments/20090310/4c09b6c4/attachment.html 


More information about the IPython-dev mailing list