Hi,
In a stack trace, is it possible to somehow get the arguments with
which each function was called?
So for example, if function `foo` in module `bar` was called with
arguments `(1, [2])` when it raised an exception, then instead of:
Traceback (most recent call last):
File bar.py,
On 2011-06-07, Dun Peal dunpea...@gmail.com wrote:
Hi,
In a stack trace, is it possible to somehow get the arguments with
which each function was called?
So for example, if function `foo` in module `bar` was called with
arguments `(1, [2])` when it raised an exception, then instead of:
On Jun 7, 1:23 pm, Neil Cerutti ne...@norwich.edu wrote:
Use pdb.
Neil, thanks for the tip; `pdb` is indeed a great debugging tool.
Still, it doesn't obviate the need for arguments in the stack trace.
For example:
1) Arguments in stack trace can expedite a debugging session, and even
obviate
On Tue, Jun 7, 2011 at 1:31 PM, Dun Peal dunpea...@gmail.com wrote:
On Jun 7, 1:23 pm, Neil Cerutti ne...@norwich.edu wrote:
Use pdb.
Neil, thanks for the tip; `pdb` is indeed a great debugging tool.
Still, it doesn't obviate the need for arguments in the stack trace.
Your program could use
On 7-6-2011 21:31, Dun Peal wrote:
On Jun 7, 1:23 pm, Neil Cerutti ne...@norwich.edu wrote:
Use pdb.
Neil, thanks for the tip; `pdb` is indeed a great debugging tool.
Still, it doesn't obviate the need for arguments in the stack trace.
If you can't use pdb perhaps you can use the
On 2011-06-07, Dun Peal dunpea...@gmail.com wrote:
On Jun 7, 1:23?pm, Neil Cerutti ne...@norwich.edu wrote:
Use pdb.
Neil, thanks for the tip; `pdb` is indeed a great debugging
tool.
Still, it doesn't obviate the need for arguments in the stack
trace. For example:
1) Arguments in stack
En Tue, 07 Jun 2011 15:09:54 -0300, Dun Peal dunpea...@gmail.com
escribió:
In a stack trace, is it possible to somehow get the arguments with
which each function was called?
So for example, if function `foo` in module `bar` was called with
arguments `(1, [2])` when it raised an exception,