You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been using IPython for a about a 1 - 1.5 years now, and I just read that IPython documentation says:
You can print variables, see code, execute statements and even walk up and down the call stack to track down the true source of the problem (which often is many layers in the stack above where the exception gets triggered).
How can I walk up and down the call stack when an error (exception) occurs?
Also, how can I do that also from an embedded shell?
The text was updated successfully, but these errors were encountered:
The documentation tells you a few lines higher:
The %pdb command allows you to toggle on and off the automatic invocation of an IPython-enhanced pdb debugger
the debugger has the same commands as pdb, (up, down frame #number) see its documentation.
This is a question better suited for the ipython-user mailing list than the bug tracker, thus closing.
I have been using IPython for a about a 1 - 1.5 years now, and I just read that IPython documentation says:
How can I walk up and down the call stack when an error (exception) occurs?
Also, how can I do that also from an embedded shell?
The text was updated successfully, but these errors were encountered: