hi Mike, thanks, for your reaction. In the meanwhile I've tried, pdp, could not get it to work with web2py (is it possible at all ??) winpdb, as you describe works perfect with web2py. Re-sync of changed source files seems essential to me, but isn't that done by just restarting the debugger (and of course it would be nice if it stepped to the point where you restarted).
cheers, Stef On 29-08-2010 14:44, Michael Ellis wrote: > I do all my development in a web2py instance running under winpdb on > OS X 10.6. It's been a huge help to always have instant access to > debugging and so far, I haven't seen any significant slowdown in > performance. > > Winpdb can be a bit of a pain to install because of the WxPython > dependencies, but that only affects the GUI side. As you're probably > aware, winpdb is actually two programs. The guts of the debugger is > rpdb2. That's what get's wrapped around the program you're > debugging. AFAIK, it doesn't have any special dependencies. The > winpdb gui is a client that attaches to it. > > Since you're developing an IDE, you might want to consider modifying > or re-implementing the winpdb interface within your application so it > can spawn and attach to rpdb2. Perhaps you can solve the problem of > re-syncing to changed source files which, to my mind, is the only real > annoyance with the winpdb gui. > > Cheers, > Mike > > On Aug 27, 4:18 pm, Stef Mientki <[email protected]> wrote: >> hello, >> >> I'm looking if I can embed debugging in Web2Py_CC, >> but I've a few questions before I start my attempts. >> >> 1. What is the allowed / preferred debugger, pdb or winpdb ? >> >> 2. A run some tests in a debugger (winpdb) and saw that exceptions are >> caught always in web2py >> (which might be a very logical choice). >> Is it possible to let the exceptions be handled by an external debugger ? >> >> 3. Is it possible to redirect the output so print statements can be seen ? >> (btw where are print statements going now ?) >> >> thanks, >> Stef Mientki
