Debugging in Python

Debugging is a critical skill for every programmer, yet it's often left to individuals to figure it out on their own. Experience definitely plays a significant role in debugging, but there's also a lot people can learn about debugging without having to wait for the next bug to appear in the projects you're working on.

This series helps you develop a clear, consistent approach to debugging. This approach should help you address small bugs quickly and efficiently, while also expanding your ability to take on more complex bugs.

The posts in this series (except for the first one) will only be available to paid subscribers for the first 6 weeks. After that they will be available to everyone. Thank you to everyone who supports my ongoing work on Mostly Python.

This is an ongoing series:

MP 138: What will be covered in this series? What does your current approach to debugging look like?

MP 139: How do you develop a consistent approach to debugging, when the size and complexity of a new bug is not yet known? What kind of information should you gather when a bug first appears, or someone reports a new bug?

MP 140: How do you work through a "simple" bug? How can you introduce bugs into a project to practice debugging? How do you read a short traceback? This post will go out Thursday, May 1.