How to Add a Breakpoint in Jupyter Notebook

Debugging is a crucial aspect of programming that allows us to track down issues in our code. Setting breakpoints helps in pausing the code execution to inspect the current state, check variable values, and step through our code line by line. In Jupyter Notebooks, debugging can be done interactively using the ipdb library, which is designed for interactive environments like notebooks.

In this article, we’ll explore how to set and use breakpoints in Jupyter Notebook effectively.

Using the ipdb Package for the addition of breakpoint in Jupyter Notebook

Although Python's built-in breakpoint() function (available in Python 3.7 and later) is designed to pause the execution of code for debugging, it may not always work as expected in Jupyter Notebook due to the interactive nature of the environment.

To reliably set breakpoints in Jupyter Notebook, we use the ipdb package, which is specifically designed for interactive debugging in environments like Jupyter. ipdb.set_trace() allows us to pause the execution of our code and enter an interactive debugging session.

Steps to Use ipdb in Jupyter:

Install the ipdb package: If we don’t have the ipdb package installed, we can install it using the following command:

!pip install ipdb

Set a Breakpoint with ipdb.set_trace(): After installing ipdb, we can replace breakpoint() with ipdb.set_trace() in our code. When the execution reaches this line, the program will pause, and we can interactively inspect variables and step through our code.

Example:

Output:

Key Features of ipdb:

• Interactive Debugging Session: We can inspect variables and execute commands interactively within the Jupyter Notebook interface.
• Step Through Code: Use commands like next (or n) to move through our code line-by-line.

The %debug Magic Command for Post-Mortem Debugging

In addition to using ipdb.set_trace() to set breakpoints at specific locations in our code, Jupyter Notebooks also provide the %debug magic command. This command allows us to inspect the state of the program after an exception is raised, enabling post-mortem debugging.

Using %debug:

• Run a piece of code that raises an exception.
• Once the error occurs, type %debug in a new cell and execute it.
• Jupyter will open an interactive debugging session where we can inspect variables and navigate the stack trace.

Example:

Output:

After running this code, a ZeroDivisionError will occur. To enter the debugging session, we would type %debug in the next cell:

Output:

We can then inspect variables like a and b, and step through the execution to understand the cause of the error.

Example of Setting a Breakpoint with ipdb

Let’s now walk through a complete example using ipdb to set a breakpoint and inspect the execution of the code interactively.

Example Code:

Output:

Explanation:

• Setting the Breakpoint: The execution will pause every time the loop encounters the ipdb.set_trace() line, allowing us to inspect the current values of num and total.
• Interactive Debugging: Once the execution pauses, we can check the values of variables by typing their names (e.g., num or total), step through the code using next, or continue execution with continue.

Debugging Commands:

• next (or n): Move to the next line in the current function.
• continue (or c): Continue the program until the next breakpoint or the end of the program.
• quit: Exit the debugging session.
• p variable_name: Print the value of a specific variable (e.g., p total).

Conclusion

Setting breakpoints is a crucial debugging technique, and using ipdb.set_trace() is a reliable way to add breakpoints in Jupyter Notebooks. While Python’s built-in breakpoint() may not always work in Jupyter, ipdb offers interactive debugging capabilities that integrate smoothly with the notebook interface. Additionally, the %debug magic command allows for post-mortem debugging when errors occur. Together, these tools can greatly improve our debugging experience in Jupyter Notebooks.