Project 1: Expense Tracker with CSV in Python

In this intermediate project, we synthesize multiple concepts covered across the curriculum—File Handling with CSV, Context Managers, Dictionary Comprehensions, Exception Handling, and the datetime module—to construct a production-ready Command-Line Personal Finance & Expense Tracker.

1. Project Requirements & Architecture

The application provides persistent financial tracking stored in expenses.csv:

1. 1
   Storage Layer: Uses csv.DictReader and csv.DictWriter with explicit newline='' and utf-8 encoding.
2. 2
   Data Model:

• id: Unique sequential transaction identifier.
• date: ISO timestamp formatted as YYYY-MM-DD.
• category: Classification (Food, Utilities, Rent, Entertainment, Travel, Health).
• amount: Floating-point expenditure.
• description: Notes explaining the transaction.

1. 1
   Analytics Engine:

• Computes monthly burn rate and category aggregations using dictionary comprehensions.
• Identifies budget trends and highest expenditure items.

1. 1
   Resilient CLI: Validates currency formats, prevents empty inputs, and handles missing files cleanly.

2. Complete Project Implementation

3. Sample Execution Simulation

Multiple Choice Questions

1. In this project, what ensures that sequential IDs never collide when generating a new expense?

A. Generating a random integer B. Calculating max([e['id'] for e in expenses], default=0) + 1 C. Asking the user to pick an ID D. Reading system clock milliseconds Answer: B Explanation: Finding the maximum existing ID and adding 1 guarantees unique, monotonic incrementing IDs.

2. How does the program validate user date input strings?

A. By regular expression matching B. By calling datetime.strptime(date_input, "%Y-%m-%d") inside a try-except ValueError block C. By comparing lengths D. Dates cannot be validated in Python Answer: B Explanation: datetime.strptime() attempts to parse the string according to the calendar format, raising ValueError if illegal.

3. Which data structure from the collections module simplifies accumulating category totals without initialization checks?

A. collections.OrderedDict B. collections.defaultdict(float) C. collections.deque D. collections.namedtuple Answer: B Explanation: defaultdict(float) initializes missing category keys to 0.0, allowing direct accumulation (category_totals[cat] += amount).

4. What happens if expenses.csv does not exist when the user launches the application?

A. The application raises an unhandled FileNotFoundError B. initialize_storage() creates the file and writes the column headers using csv.DictWriter C. Python prompts the user to insert a USB drive D. The script halts with an exit code 1 Answer: B Explanation: initialize_storage() checks for the file's presence and initializes it with headers if absent.

5. Why must amount be converted using float(row['amount']) after reading from CSV?

A. CSV format stores all values strictly as strings in text mode B. To round numbers to the nearest integer C. Float conversion is required by Python's static type checker D. To prevent buffer overflows Answer: A Explanation: Flat CSV files store plain text; numeric columns must be explicitly parsed from strings to floats for arithmetic.