Stop scattering print() statements to figure out what your code is doing. In this video, I debug a real Python error — a KeyError from inconsistent gNMI response data — using the VS Code debugger instead of print(). I walk through breakpoints, the variables panel, watch expressions, the debug console, conditional breakpoints, and logpoints, all while solving a real bug in a script that talks to an IOS-XR device on the free Cisco DevNet Always-On Sandbox.
🔗 Resources:
DevNet Always-On Sandbox (IOS-XR): https://devnetsandbox.cisco.com/DevNet/
Demo scripts (broken + fixed): https://github.com/jillesca/debug_pyt...
VS Code Debugging docs: https://code.visualstudio.com/docs/ed...
VS Code Python Debugging: https://code.visualstudio.com/docs/py...
uv (Python package manager): https://docs.astral.sh/uv/
#DeveloperProductivity #CiscoDevNet #NetworkAutomation #PythonDebugging
Table of Contents:
01:48 - Quick Setup
03:25 - Debugger Navigation
03:44 - Setting the breakpoint
06:19 - Watch Expressions
07:35 - The Debug Console — Exploring the Data
11:35 - Conditional Breakpoints
12:55 - Logpoints
14:04 - Recap
On this page of the site you can watch the video online Debug Python the right way with a duration of hours minute second in good quality, which was uploaded by the user Cisco DevNet 24 April 2026, share the link with friends and acquaintances, this video has already been watched 357 times on youtube and it was liked by 18 viewers. Enjoy your viewing!