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
In questa pagina del sito puoi guardare il video online Debug Python the right way della durata di ore minuti seconda in buona qualità , che l'utente ha caricato Cisco DevNet 24 aprile 2026, condividi il link con amici e conoscenti, su youtube questo video è già stato visto 357 volte e gli è piaciuto 18 spettatori. Buona visione!