Error Handling: Making Robust Python Programs

Error Handling: Making Robust Python Programs

Learn to write robust Python programs that handle errors gracefully. Master try-except blocks, create custom exceptions, use assertions, and implement logging for production-quality code.

Understanding Exceptions in Python

Exceptions are events that disrupt normal program flow. Python's exception hierarchy allows precise error handling.

# Common exceptions
try: # ValueError: converting incompatible type age = int('not a number')
except ValueError as e: print(f'Error: {e}')

try: # ZeroDivisionError: dividing by zero result = 10 / 0
except ZeroDivisionError: print('Cannot divide by zero')

try: # IndexError: accessing non-existent index lst = [1, 2, 3] print(lst[10])
except IndexError: print('Index out of range')

try: # KeyError: accessing non-existent dictionary key d = {'name': 'Aditya'} print(d['age'])
except KeyError: print('Key does not exist')

try: # FileNotFoundError: opening non-existent file with open('missing.txt', 'r') as f: content = f.read()
except FileNotFoundError: print('File not found') 

Try-Except-Else-Finally Structure

A complete exception handling structure with optional else and finally blocks.

try: # Code that might raise an exception num = int(input('Enter a number: ')) result = 100 / num
except ValueError: # Handles ValueError specifically print('Error: Please enter a valid number')
except ZeroDivisionError: # Handles ZeroDivisionError specifically print('Error: Cannot divide by zero')
except Exception as e: # Catches any other exception print(f'Unexpected error: {e}')
else: # Runs only if no exception occurred print(f'Result: {result}')
finally: # Always runs, whether exception occurred or not print('Cleanup code runs here')

# Output if user enters 0:
# Error: Cannot divide by zero
# Cleanup code runs here 

Real-World Example: Validating Indian Identity Numbers

Indian identity systems use various formats like Aadhaar and PAN that require validation.

def validate_aadhar(aadhar): '''Validate Indian Aadhaar number format''' try: if not isinstance(aadhar, str): raise TypeError('Aadhaar must be a string') if len(aadhar) != 12: raise ValueError('Aadhaar must be 12 digits') if not aadhar.isdigit(): raise ValueError('Aadhaar must contain only digits') return True except (TypeError, ValueError) as e: print(f'Invalid Aadhaar: {e}') return False

def validate_pan(pan): '''Validate Indian PAN format: AAAAA9999A''' try: if not isinstance(pan, str): raise TypeError('PAN must be a string') if len(pan) != 10: raise ValueError('PAN must be 10 characters') # First 5 characters should be letters if not pan[:5].isalpha(): raise ValueError('First 5 characters must be letters') # Next 4 characters should be digits if not pan[5:9].isdigit(): raise ValueError('Characters 6-9 must be digits') # Last character should be letter if not pan[9].isalpha(): raise ValueError('Last character must be a letter') return True except (TypeError, ValueError) as e: print(f'Invalid PAN: {e}') return False

# Testing validation functions
print(validate_aadhar('123456789012'))  # True
print(validate_aadhar('1234567890')) # False - too short
print(validate_aadhar('12345678901a')) # False - contains letter

print(validate_pan('ABCDE1234F')) # True
print(validate_pan('ABCDE123')) # False - too short
print(validate_pan('12345678901')) # False - wrong format 

Custom Exceptions

Create custom exceptions for domain-specific errors in your application.

# Define custom exceptions
class InvalidMarksError(Exception): '''Raised when marks are outside valid range''' pass

class StudentNotFoundError(Exception): '''Raised when student record not found''' pass

class InsufficientAttendanceError(Exception): '''Raised when attendance is below minimum required''' pass

# Using custom exceptions
class Student: def __init__(self, roll_no, name, marks): self.roll_no = roll_no self.name = name self.marks = marks def set_marks(self, marks): if not isinstance(marks, (int, float)): raise TypeError('Marks must be a number') if marks < 0 or marks > 100: raise InvalidMarksError(f'Marks must be between 0 and 100, got {marks}') self.marks = marks def check_exam_eligibility(self, attendance): if attendance < 75: raise InsufficientAttendanceError( f'Attendance {attendance}% is below 75% requirement' ) return True

# Handling custom exceptions
try: student = Student(101, 'Aditya', 85) student.set_marks(105)  # This will raise InvalidMarksError
except InvalidMarksError as e: print(f'Marks Error: {e}')
except TypeError as e: print(f'Type Error: {e}')

try: student.check_exam_eligibility(70)
except InsufficientAttendanceError as e: print(f'Eligibility Error: {e}') 

Using Assertions for Debugging

Assertions check conditions during development and can be disabled in production.

def calculate_percentage(marks, total): '''Calculate percentage with assertions for validation''' assert isinstance(marks, (int, float)), 'Marks must be a number' assert isinstance(total, (int, float)), 'Total must be a number' assert marks >= 0, 'Marks cannot be negative' assert total > 0, 'Total must be positive' assert marks <= total, 'Marks cannot exceed total' return (marks / total) * 100

# Testing assertions
print(calculate_percentage(45, 50))  # 90.0

try: print(calculate_percentage(60, 50))  # AssertionError: Marks cannot exceed total
except AssertionError as e: print(f'Assertion failed: {e}')

# Disabling assertions in production (Python -O flag)
# python -O script.py  # Assertions are ignored 

Logging for Debugging and Monitoring

Use logging instead of print statements for production-quality error tracking.

import logging

# Configure logging
logging.basicConfig( level=logging.DEBUG, format='%(asctime)s - %(levelname)s - %(message)s'
)

logger = logging.getLogger(__name__)

def process_student_data(student_file): '''Process student data with comprehensive logging''' try: logger.info(f'Starting to process file: {student_file}') with open(student_file, 'r') as f: students = f.readlines() logger.debug(f'Read {len(students)} student records') processed = 0 for line in students: try: roll_no, name, marks = line.strip().split(',') marks = int(marks) logger.debug(f'Processed: {name} with marks {marks}') processed += 1 except ValueError as e: logger.warning(f'Skipping invalid line: {line.strip()} - {e}') continue logger.info(f'Successfully processed {processed}/{len(students)} records') return processed except FileNotFoundError: logger.error(f'File not found: {student_file}') raise except Exception as e: logger.critical(f'Unexpected error: {e}') raise

# Logging levels:
# DEBUG - Detailed information (10)
# INFO - General information (20)
# WARNING - Warning messages (30)
# ERROR - Error messages (40)
# CRITICAL - Critical errors (50)

logger.debug('This is a debug message')
logger.info('This is info')
logger.warning('This is a warning')
logger.error('This is an error')
logger.critical('This is critical') 

Debugging Strategies

Practice Problems

1. Create a function that validates a phone number format and raises appropriate exceptions.
2. Write a program that reads student marks from a file and handles missing or invalid data gracefully.
3. Create custom exceptions for a banking system (InsufficientFunds, InvalidAccount, etc.)
4. Implement a function with logging that processes multiple files and logs warnings for errors.
5. Write a program that uses assertions to validate function inputs and document expected behavior.

Key Takeaways

• Use try-except blocks to handle specific exceptions gracefully
• Create custom exceptions for domain-specific errors in your application
• Use finally block for cleanup code that must always run
• Implement logging for production-quality error tracking and debugging
• Use assertions during development to validate assumptions and inputs

Under the Hood: Error Handling: Making Robust Python Programs

Here is what separates someone who merely USES technology from someone who UNDERSTANDS it: knowing what happens behind the screen. When you tap "Send" on a WhatsApp message, do you know what journey that message takes? When you search something on Google, do you know how it finds the answer among billions of web pages in less than a second? When UPI processes a payment, what makes sure the money goes to the right person?

Understanding Error Handling: Making Robust Python Programs gives you the ability to answer these questions. More importantly, it gives you the foundation to BUILD things, not just use things other people built. India's tech industry employs over 5 million people, and companies like Infosys, TCS, Wipro, and thousands of startups are all built on the concepts we are about to explore.

This is not just theory for exams. This is how the real world works. Let us get into it.

Object-Oriented Programming: Modelling the Real World

OOP lets you model real-world entities as code "objects." Each object has properties (data) and methods (behaviour). Here is a practical example:

class BankAccount: """A simple bank account — like what SBI or HDFC uses internally""" def __init__(self, holder_name, initial_balance=0): self.holder = holder_name self.balance = initial_balance # Private in practice self.transactions = [] # History log def deposit(self, amount): if amount <= 0: raise ValueError("Deposit must be positive") self.balance += amount self.transactions.append(f"+₹{amount}") return self.balance def withdraw(self, amount): if amount > self.balance: raise ValueError("Insufficient funds!") self.balance -= amount self.transactions.append(f"-₹{amount}") return self.balance def statement(self): print(f"
--- Account Statement: {self.holder} ---") for t in self.transactions: print(f"  {t}") print(f"  Balance: ₹{self.balance}")

# Usage
acc = BankAccount("Rahul Sharma", 5000)
acc.deposit(15000) # Salary credited
acc.withdraw(2000) # UPI payment to Swiggy
acc.withdraw(500) # Metro card recharge
acc.statement()

This is encapsulation — bundling data and behaviour together. The user of BankAccount does not need to know HOW deposit works internally; they just call it. Inheritance lets you extend this: a SavingsAccount could inherit from BankAccount and add interest calculation. Polymorphism means different account types can respond to the same .withdraw() method differently (savings accounts might check minimum balance, current accounts might allow overdraft).

Real-World System Design: Swiggy's Architecture

When you order food on Swiggy, here is what happens behind the scenes in about 2 seconds: your location is geocoded (algorithms), nearby restaurants are queried from a spatial index (data structures), menu prices are pulled from a database (SQL), delivery time is estimated using ML models trained on historical data (AI), the order is placed in a distributed message queue (Kafka), a delivery partner is assigned using a matching algorithm (optimization), and real-time tracking begins using WebSocket connections (networking). EVERY concept in your CS curriculum is being used simultaneously to deliver your biryani.

How the Web Request Cycle Works

Every time you visit a website, a precise sequence of events occurs. Here is the flow:

 You (Browser) DNS Server Web Server | | | |---[1] bharath.ai --->| | | | | |<--[2] IP: 76.76.21.9| | | | | |---[3] GET /index.html ----------------->  | | | | | | [4] Server finds file, | | runs server code, | | prepares response | | | |<---[5] HTTP 200 OK + HTML + CSS + JS --- | | | | [6] Browser parses HTML | Loads CSS (styling) | Executes JS (interactivity) | Renders final page |

Step 1-2 is DNS resolution — converting a human-readable domain name to a machine-readable IP address. Step 3 is the HTTP request. Step 4 is server-side processing (this is where frameworks like Node.js, Django, or Flask operate). Step 5 is the HTTP response. Step 6 is client-side rendering (this is where React, Angular, or Vue operate).

In a real-world scenario, this cycle also involves CDNs (Content Delivery Networks), load balancers, caching layers, and potentially microservices. Indian companies like Jio use this exact architecture to serve 400+ million subscribers.

Production Engineering: Error Handling: Making Robust Python Programs at Scale

Understanding error handling: making robust python programs at an academic level is necessary but not sufficient. Let us examine how these concepts manifest in production environments where failure has real consequences.

Consider India's UPI system processing 10+ billion transactions monthly. The architecture must guarantee: atomicity (a transfer either completes fully or not at all — no half-transfers), consistency (balances always add up correctly across all banks), isolation (concurrent transactions on the same account do not interfere), and durability (once confirmed, a transaction survives any failure). These are the ACID properties, and violating any one of them in a payment system would cause financial chaos for millions of people.

At scale, you also face the thundering herd problem: what happens when a million users check their exam results at the same time? (CBSE result day, anyone?) Without rate limiting, connection pooling, caching, and graceful degradation, the system crashes. Good engineering means designing for the worst case while optimising for the common case. Companies like NPCI (the organisation behind UPI) invest heavily in load testing — simulating peak traffic to identify bottlenecks before they affect real users.

Monitoring and observability become critical at scale. You need metrics (how many requests per second? what is the 99th percentile latency?), logs (what happened when something went wrong?), and traces (how did a single request flow through 15 different microservices?). Tools like Prometheus, Grafana, ELK Stack, and Jaeger are standard in Indian tech companies. When Hotstar streams IPL to 50 million concurrent users, their engineering team watches these dashboards in real-time, ready to intervene if any metric goes anomalous.

The career implications are clear: engineers who understand both the theory (from chapters like this one) AND the practice (from building real systems) command the highest salaries and most interesting roles. India's top engineering talent earns ₹50-100+ LPA at companies like Google, Microsoft, and Goldman Sachs, or builds their own startups. The foundation starts here.

Key Vocabulary

Here are important terms from this chapter that you should know:

💡 Interview-Style Problem

Here is a problem that frequently appears in technical interviews at companies like Google, Amazon, and Flipkart: "Design a URL shortener like bit.ly. How would you generate unique short codes? How would you handle millions of redirects per second? What database would you use and why? How would you track click analytics?"

Think about: hash functions for generating short codes, read-heavy workload (99% redirects, 1% creates) suggesting caching, database choice (Redis for cache, PostgreSQL for persistence), and horizontal scaling with consistent hashing. Try sketching the system architecture on paper before looking up solutions. The ability to think through system design problems is the single most valuable skill for senior engineering roles.

Where This Takes You

The knowledge you have gained about error handling: making robust python programs is directly applicable to: competitive programming (Codeforces, CodeChef — India has the 2nd largest competitive programming community globally), open-source contribution (India is the 2nd largest contributor on GitHub), placement preparation (these concepts form 60% of technical interview questions), and building real products (every startup needs engineers who understand these fundamentals).

India's tech ecosystem offers incredible opportunities. Freshers at top companies earn ₹15-50 LPA; experienced engineers at FAANG companies in India earn ₹50-1 Cr+. But more importantly, the problems being solved in India — digital payments for 1.4 billion people, healthcare AI for rural areas, agricultural tech for 150 million farmers — are some of the most impactful engineering challenges in the world. The fundamentals you are building will be the tools you use to tackle them.

Crafted for Class 7–9 • Python Mastery • Aligned with NEP 2020 & CBSE Curriculum