Errors, Exceptions & Debugging: Finding and Fixing Code Flaws

01-06 What is an Error & 3 Fundamental Categories

Simply stated: An error is any defect, violation, or anomaly that prevents a program from functioning as intended or forces execution to abort. All computational errors classify into three distinct species:

Reading and Rectifying Syntax Errors

When Python's interpreter encounters syntax violations during initial parsing, it points directly to the offending token with a caret indicator:

07-11 Runtime Errors, Common Exceptions & Decoding Tracebacks

When syntactically valid code attempts an operation that the runtime environment or math primitives cannot satisfy, Python raises an Exception:

What is a Traceback? Navigating the Call Stack

When an unhandled exception halts execution, Python emits a Traceback. This is a chronological call stack history tracing how execution navigated through function boundaries to reach the scene of the crash:

12-20 try, except, else & finally Control Flow

Production applications cannot terminate simply because a user made a typo. Python intercepts exceptions through the defensive try / except construct:

Catching Multiple Distinct Exceptions

Complex blocks may encounter disparate failure modes. Distinguishing between errors allows customized recovery paths:

21-24 Specific Exceptions, raise & Input Validation

Blindly catching all exceptions under a monolithic block is one of the most perilous traps in software engineering:

Enforcing Business Rules with raise

Even if Python considers an operation mathematically legal, domain rules may prohibit it. Developers use raise to enforce program invariants:

25-26 Logical Errors: The Silent Killer & Comparative Matrix

Logical errors never trigger a red stack trace; they run smoothly and generate erroneous data in silence:

27-33 Systematic Debugging Methodology, Breakpoints & Evidence

Debugging is not haphazard code mutation. It is a forensic, evidence-driven scientific process:

Expected vs. Actual Technique

The most reliable heuristic for isolating elusive bugs is establishing two rigorous columns:

Debuggers & Breakpoints

While print() diagnostics suffice for brief scripts, large scale systems demand interactive Debuggers:

• Breakpoint: An intentional pause point placed on a line of source code. Execution freezes immediately prior to line evaluation.
• Step Over / Step Into: Advancing execution line-by-line while inspecting variables, memory offsets, and call frames live in memory.

34-39 Exception Architecture & Stack Propagation

When an inner function encounters an exception without a local handler, the exception bubbles up through caller frames via Exception Propagation:

40-42 Complete Robust Pipeline & Testing vs. Debugging

Synthesizing input parsing, type casting, domain validation, and exception interceptors into a bulletproof input routine:

Testing vs. Debugging: Clarifying the Frontier

43-44 The 9 Diagnostic Questions for Developers

When an unhandled exception strikes your terminal, remain composed and systematically answer these 9 questions:

Test your diagnostic intuition against real-world errors. Expand each accordion to examine reference solutions:

# Flawed:
# for i in range(5)
#     print(i)

# Corrected with terminal colon:
for i in range(5):
    print(i)

try:
    number = int(input("Enter an integer: "))
    print(f"Squared: {number ** 2}")
except ValueError:
    print("Invalid format! Please enter numeric digits only.")

try:
    divisor = float(input("Enter divisor: "))
    result = 100 / divisor
    print(f"Result: {result}")
except ZeroDivisionError:
    print("Math Error: Division by zero is undefined.")
except ValueError:
    print("Invalid numeric value.")

fruits = ["Apple", "Banana", "Mango"]
try:
    idx = int(input("Enter index (0-2): "))
    print(f"Fruit: {fruits[idx]}")
except IndexError:
    print(f"Index out of range! Valid range is 0 to {len(fruits) - 1}.")
except ValueError:
    print("Please enter a valid integer index.")

user = {"name": "Salim", "age": 25}

# Pattern 1: try / except
try:
    print(user["email"])
except KeyError:
    print("Property 'email' does not exist in user profile.")

# Pattern 2: Pythonic .get() fallback
print(user.get("email", "Not Provided"))

filename = input("Enter file to load: ")
try:
    with open(filename, "r", encoding="utf-8") as f:
        print(f.read())
except FileNotFoundError:
    print(f"Error: Could not locate '{filename}' on disk.")

price = 500
quantity = 4
discount_percent = 10

# Faulty line was: subtotal = price + quantity
# Correct calculation:
subtotal = price * quantity
discount_amount = subtotal * (discount_percent / 100)
final_price = subtotal - discount_amount

print(f"Correct Total: ${final_price:.2f}")  # Output: $1800.00

def safe_calculator():
    try:
        a = float(input("First number: "))
        op = input("Operation (+, -, *, /): ").strip()
        b = float(input("Second number: "))

        if op == "+": return a + b
        elif op == "-": return a - b
        elif op == "*": return a * b
        elif op == "/":
            if b == 0: raise ZeroDivisionError
            return a / b
        else:
            print("Invalid operator!")
            return None
    except ValueError:
        print("Inputs must be numbers!")
    except ZeroDivisionError:
        print("Cannot divide by zero!")

print(f"Result: {safe_calculator()}")