Python Classes & OOP — Modeling Your World in Code

Classes let you bundle data with the behavior that operates on it. You'll build a class for a real thing and use AI to refactor it with confidence.

50 min · Reviewed 2026

When functions aren't enough

A function takes inputs and returns outputs. A class groups related functions with the data they share, so you stop passing the same five arguments to every call. In 2026 Python, @dataclass makes writing classes almost free.

from dataclasses import dataclass, field from datetime import datetime @dataclass class Task: title: str priority: int = 3 done: bool = False created_at: datetime = field(default_factory=datetime.now) def complete(self) -> None: self.done = True def age_seconds(self) -> float: return (datetime.now() - self.created_at).total_seconds() t = Task("Write essay", priority=1) t.complete() print(t) # Task(title='Write essay', priority=1, done=True, )@dataclass auto-generates __init__, __repr__, and __eq__. No boilerplate.

self, methods, and instance data

self is the first parameter of every instance method — Python passes the instance in automatically
Methods are just functions that live inside a class
Instance attributes are scoped to one object; class attributes are shared

Inheritance — build on what exists

@dataclass class RecurringTask(Task): interval_days: int = 7 def next_due(self) -> datetime: from datetime import timedelta return self.created_at + timedelta(days=self.interval_days) r = RecurringTask("Water plants", interval_days=3) print(r.next_due()) r.complete() # inherited from TaskRecurringTask gets everything Task has, plus new fields and methods.

Error handling with typed exceptions

class TaskError(Exception): """Base class for task errors.""" class TaskAlreadyDoneError(TaskError): pass @dataclass class SafeTask(Task): def complete(self) -> None: if self.done: raise TaskAlreadyDoneError(f"{self.title!r} is already done") self.done = True try: t = SafeTask("Study") t.complete() t.complete() # second call raises except TaskAlreadyDoneError as e: print(f"Caught: {e}")Custom exceptions let callers handle specific failures without parsing error strings.

Mini-exercise

Design a BankAccount @dataclass with owner, balance, and transactions (list)
Add methods deposit(amount) and withdraw(amount)
withdraw should raise InsufficientFundsError if balance < amount
Have your AI assistant write unit tests for the happy and failure paths

Plain function	Class
Stateless	Holds state
Easy to test	Still easy with dataclass
Good for: one-shot logic	Good for: long-lived things (users, accounts, sessions)
No setup cost	A little boilerplate, a lot of clarity

Big idea: classes model the nouns of your program. When you find yourself passing the same blob of data everywhere, it wants to be a class.

End-of-lesson check

8 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-prog-python-oop-creators

What is the main idea of "Python Classes & OOP — Modeling Your World in Code"?
1. Classes let you bundle data with the behavior that operates on it. You'll build a class for a real thing and use AI to refactor it with confidence.
2. Use AI as the final authority for the whole decision
3. Avoid checking the answer once it sounds polished
4. Focus only on speed instead of judgment
Which concept is most central to "Python Classes & OOP — Modeling Your World in Code"?
1. instance
2. class
3. dataclass
4. method
Which use of AI fits this topic best?
1. Let the AI decide what matters without your review
2. Use the answer before checking whether it fits the situation
3. self is the first parameter of every instance method — Python passes the instance in automatically
4. Treat the AI output as automatically correct
What should a careful learner remember about "Advanced: when to prefer composition"?
1. Use AI to draft or organize ideas about class, then verify before acting.
2. Skip the context so the tool can guess faster
3. Treat the output as private even after sharing it online
4. Use the answer without checking the source
You want to use AI after this lesson. What is the safest next step?
1. Act immediately because the AI answer is written clearly
2. Use AI for drafting and comparison, but verify before publishing or relying on it.
3. Hide uncertainty so the final answer looks cleaner
4. Use private or sensitive details before checking permission
How should AI output about class be treated?
1. As proof that no other source is needed
2. As a replacement for context, consent, or expert review
3. As a draft or helper output that still needs human judgment and verification
4. As something that becomes correct when it sounds confident
Name one way to verify an AI answer about class.
Which action would help you apply "Python Classes & OOP — Modeling Your World in Code" responsibly?
1. Use the tool to avoid thinking through the tradeoff
2. Keep going even if the output conflicts with a trusted source
3. Treat the AI output as automatically correct
4. Methods are just functions that live inside a class

← Back to interactive lesson

Tendril · Creators · AI-Assisted Coding

Python Classes & OOP — Modeling Your World in Code

Classes let you bundle data with the behavior that operates on it. You'll build a class for a real thing and use AI to refactor it with confidence.

50 min · Reviewed 2026

When functions aren't enough

from dataclasses import dataclass, field from datetime import datetime @dataclass class Task: title: str priority: int = 3 done: bool = False created_at: datetime = field(default_factory=datetime.now) def complete(self) -> None: self.done = True def age_seconds(self) -> float: return (datetime.now() - self.created_at).total_seconds() t = Task("Write essay", priority=1) t.complete() print(t) # Task(title='Write essay', priority=1, done=True, )@dataclass auto-generates __init__, __repr__, and __eq__. No boilerplate.

self, methods, and instance data

self is the first parameter of every instance method — Python passes the instance in automatically
Methods are just functions that live inside a class
Instance attributes are scoped to one object; class attributes are shared

Inheritance — build on what exists

@dataclass class RecurringTask(Task): interval_days: int = 7 def next_due(self) -> datetime: from datetime import timedelta return self.created_at + timedelta(days=self.interval_days) r = RecurringTask("Water plants", interval_days=3) print(r.next_due()) r.complete() # inherited from TaskRecurringTask gets everything Task has, plus new fields and methods.

Error handling with typed exceptions

class TaskError(Exception): """Base class for task errors.""" class TaskAlreadyDoneError(TaskError): pass @dataclass class SafeTask(Task): def complete(self) -> None: if self.done: raise TaskAlreadyDoneError(f"{self.title!r} is already done") self.done = True try: t = SafeTask("Study") t.complete() t.complete() # second call raises except TaskAlreadyDoneError as e: print(f"Caught: {e}")Custom exceptions let callers handle specific failures without parsing error strings.

Mini-exercise

Design a BankAccount @dataclass with owner, balance, and transactions (list)
Add methods deposit(amount) and withdraw(amount)
withdraw should raise InsufficientFundsError if balance < amount
Have your AI assistant write unit tests for the happy and failure paths

Plain function	Class
Stateless	Holds state
Easy to test	Still easy with dataclass
Good for: one-shot logic	Good for: long-lived things (users, accounts, sessions)
No setup cost	A little boilerplate, a lot of clarity

Big idea: classes model the nouns of your program. When you find yourself passing the same blob of data everywhere, it wants to be a class.

End-of-lesson check

8 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-prog-python-oop-creators

What is the main idea of "Python Classes & OOP — Modeling Your World in Code"?
1. Classes let you bundle data with the behavior that operates on it. You'll build a class for a real thing and use AI to refactor it with confidence.
2. Use AI as the final authority for the whole decision
3. Avoid checking the answer once it sounds polished
4. Focus only on speed instead of judgment
Which concept is most central to "Python Classes & OOP — Modeling Your World in Code"?
1. instance
2. class
3. dataclass
4. method
Which use of AI fits this topic best?
1. Let the AI decide what matters without your review
2. Use the answer before checking whether it fits the situation
3. self is the first parameter of every instance method — Python passes the instance in automatically
4. Treat the AI output as automatically correct
What should a careful learner remember about "Advanced: when to prefer composition"?
1. Use AI to draft or organize ideas about class, then verify before acting.
2. Skip the context so the tool can guess faster
3. Treat the output as private even after sharing it online
4. Use the answer without checking the source
You want to use AI after this lesson. What is the safest next step?
1. Act immediately because the AI answer is written clearly
2. Use AI for drafting and comparison, but verify before publishing or relying on it.
3. Hide uncertainty so the final answer looks cleaner
4. Use private or sensitive details before checking permission
How should AI output about class be treated?
1. As proof that no other source is needed
2. As a replacement for context, consent, or expert review
3. As a draft or helper output that still needs human judgment and verification
4. As something that becomes correct when it sounds confident
Name one way to verify an AI answer about class.
Which action would help you apply "Python Classes & OOP — Modeling Your World in Code" responsibly?
1. Use the tool to avoid thinking through the tradeoff
2. Keep going even if the output conflicts with a trusted source
3. Treat the AI output as automatically correct
4. Methods are just functions that live inside a class

← Back to interactive lesson