[Urwid] ANN: PuDB - the Python Urwid Debugger

Adam Blackburn compwiz18 at gmail.com
Tue Jun 9 11:08:58 EDT 2009

> Is the program you're debugging using urwid as well?

Not the part that I was testing it on. I can reproduce it on the debug_me.py
file included with the tarball as well, using the 0.90.3 release in both
gnome-terminal and xterm. I'll give it a try with the 0.90.4 release
tomorrow and let you know.


On Tue, Jun 9, 2009 at 10:53 PM, Andreas Klöckner
<lists at informa.tiker.net>wrote:

> On Dienstag 09 Juni 2009, you wrote:
> >  * When using the "q" key to quit, I cannot see any of the characters I
> > enter into the terminal after pudb exits until I reset the terminal using
> > the "reset" command.
> Is the program you're debugging using urwid as well? I saw some urwid code
> in
> wicd. If so, pudb and your code are fighting over the use of the alternate
> buffer, and the result is likely garbage. Fixing his depends on the "output
> hijacking" I mentioned. It's kind of ironic that Urwid code would be the
> one
> type of code which pudb doesn't usefully debug. :)
> If you're not using urwid (or other curses stuff), then I don't know. I
> can't
> reproduce this on "regular" code.
> >  * When using the "!" key to invoke a Python shell, I cannot see anything
> I
> > type and the prompt is not aligned with the left side of the screen.
> Typing
> > blindly still results in the expected output, which is also not
> > left-aligned.
> Likely the same issue as above.
> >  * For whatever reason, the __file__ variable does not exist when using
> > PuDB, which causes my test program to raise an exception that is not
> raised
> > when it is executed normally.
> Fixed.
> > I am using the Gnome terminal, Python 2.6, Urwid on Ubuntu 9.04

More information about the Urwid mailing list