Favorite recent jupyter notebook discovery - the %debug magic:
1. Get an exception.
2. Insert a new cell, type %debug and run it.
An interactive debugger will open bringing you to where the exception occurred and allowing you to look around!
1. Get an exception.
2. Insert a new cell, type %debug and run it.
An interactive debugger will open bringing you to where the exception occurred and allowing you to look around!
Type `help` for a listing of available dev superpowers. `up` takes you one level up in the stack.
You can also set a breakpoint and open the interactive debugger at an arbitrary point via doing the following.
Hint: You can set a breakpoint in scripts / libraries outside of Jupyter notebook. The debugger will open when the code is run.
You can assign new values to variables or step through the execution of the code.
`next` runs next line of code, `exit` exits the debugger.
You can assign new values to variables or step through the execution of the code.
`next` runs next line of code, `exit` exits the debugger.
This is very useful on its own, but it really shines when combined with a workflow trick I learned from @jeremyphoward.
When working on new functionality, import all you need and develop the component directly in the notebook. Exceptional debugging + ability to iterate v quickly
When working on new functionality, import all you need and develop the component directly in the notebook. Exceptional debugging + ability to iterate v quickly
