On Dec 3, 11:10 am, Amit Gupta <[EMAIL PROTECTED]> wrote: > > > Thanks Frank. But again, this results into stack-track when the > exception is caught. On the other hand, I would like the debug-trace > just before throwing the exception. As a case, I might be debugging > code, where the programmar forgot to handle an exception and it is > being caught way up in the flow (with generic catch block)
One thing that I can guess is to put a breakpoint on function "raise". I assume all of the exceptions are thrown by "raise" and raise is not a keyword, instead a function. Will it work? -- http://mail.python.org/mailman/listinfo/python-list
