On Tue, 14 Dec 2010 00:26:44 -0800, Kris Wilson <kris(a)onoku.com> wrote:
> I'm a fan of your pudb project. Recently I've been trying to use pudb
> to debug some UNIX server code but have been running into various
> problems launching pudb from the context of a server thread (as well
> as the pain of needing to be in the original python console of my
> running server app, when normally it would "daemonize"). Have you
> considered implementing a client/server model for pudb to allow for
> remote debugging using pudb as a front end (e.g. detach the curses
> console and communicate to it over the network)? I believe that this
> model would allow pudb to be a truly great debugger that would be
> "state of the art" for python debugging in a server environment.
> I'm imaging something like:
> import pudb
> pudb.set_trace_remote('127.0.0.1', 5555)
> with a server side pudb console run like:
> ./pudb -p 5555
> Let me know if you have considered this or have anything planned (or
> even any ideas on this).
I'm glad you're finding pudb useful.
It should be quite possible to do this by swapping out bdb (Python's
built-in debugging interface) for WinPDB's rpdb2. This would make pudb
effectively GPL'd--not sure if that's an issue, but so far I've tried to
avoid that. In any case, I like the idea as long as it doesn't come at
the expense of making current usage patterns harder.
Btw, you might want to consider signing up for the new PuDB mailing