I often find that I debug problems by inserting a pdb.set_trace() in code, and then quitting the debugger with "q" once I've gathered information I need to make code changes. This causes a BdbQuit exception to be raised and propagated to the test runner. The resulting traceback isn't actually useful.
I'd like to change the test runner to capture BdbQuit and print a message to stdout before exiting instead of dumping the traceback. Any reason this would be a bad idea? -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "Chaos is the score upon which reality is written." --Henry Miller _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
