[IPython-dev] making pdoc, pdef, and pinfo more generally useful (Was Re: Patches to use pydb instead of pdb for debugging)
rocky at panix.com
Thu Oct 12 17:01:40 EDT 2006
Ville M. Vainio writes:
> Yeah, a lot has been happening this last week (some of which I am only
> able to speak properly next week, but might involve much more python
> coding in my day job) and I haven't tested pydb yet. Sorry :-).
> They are in the wrong place, yes, but such refactoring may not be
> optimal for the "stable" branch. Instead, I'd like to see your patches
> for kludging the _ofind, _inspect et. al. with optional 'namespaces'
> keyword argument. I have no opposition to getting them in.
> So send out patches for whatever you've got in your working copy
> (preferably by friday) and I'll take a proper look at them.
By Friday? Gee, that doesn't leave much time, so I'll send what I have
now. Let's see, a summary of the patches. First there's what I sent
before and in private email I sent a slight code improvement on that.
In that we allowed "%pdb on" and -pdb and pm to call pydb if that's
installed and Python 2.5
Above this there's
- decorating do_up, do_down so they get the
docstrings from pydb (there are none in pdb so it's a no op). Also
do_frame decorated, but again in pdb there's no "frame" command.
- Changing the list command so that it accepts pydb/gdb syntax by decoupling
the parsing part from the listing part
- Allowing magic_pinfo, magic_pdef, and magic_pdoc to be used inside the
- There's some stuff using command pydb's completion, and this helps a
little but private email with Alexander Schmolc suggests there may
be some stygian stable work in (re)doing the issue of making command
completion work correctly.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 13940 bytes
Desc: patches to make ipython work with pydb (and other good stuff)
More information about the IPython-dev