Can a Python Dictionary Store Mixed Data Types?

[Rajeev Bagra]

—

Understanding Value Types with the Student Example

---

🔹 Initial Context

While learning Object-Oriented Programming (OOP) in Python, we often use dictionaries to store objects.

For example:

class Student:
    def __init__(self, exercises):
        self.exercises = exercises


students = {}

students["Alice"] = Student(12)
students["Bob"] = Student(7)
students["Harry"] = Student(5)

Here, every value in the dictionary is a Student object.
This is clean, predictable, and easy to manage.

However, beginners often wonder:

“Can I store other types, like numbers or strings, in the same dictionary?”

Let’s explore the answer.

---

🔹 Step 1: Python Allows Mixed Types in Dictionaries

In Python, dictionary values can be any data type.

This is valid code:

students = {}

students["Alice"] = Student(12)     # Object
students["Bob"] = 50               # Integer
students["Harry"] = "Absent"       # String
students["Emma"] = [1, 2, 3]        # List

Python will not give any error.

Why?

Because Python is dynamically typed.
Variables and containers do not enforce fixed types.

---

🔹 Step 2: What Happens Internally

Internally, the dictionary looks like this:

"Alice" → Student object
"Bob"   → Integer (50)
"Harry" → String ("Absent")
"Emma"  → List

Each key simply points to some object in memory — Python does not care what type it is.

---

🔹 Step 3: Why Mixed Types Can Cause Problems

Now imagine this code:

for name in students:
    print(students[name].exercises)

If students["Bob"] is an integer:

❌ Program crashes:

AttributeError: 'int' object has no attribute 'exercises'

Because integers do not have .exercises.

This makes your program unreliable.

---

🔹 Step 4: Example of a Bug Caused by Mixed Types

Consider:

students["Bob"] = 50

print(students["Bob"].exercises)

Result:

AttributeError

This happens at runtime, not during coding — which makes it harder to debug.

---

🔹 Step 5: Best Practice – Keep Dictionary Values Consistent

In most real programs, you should keep one type per dictionary.

Good design:

students: dict[str, Student] = {}

students["Alice"] = Student(12)
students["Bob"] = Student(7)
students["Harry"] = Student(5)

Now you can safely assume:

Every value is a Student.

This makes code easier to read and maintain.

---

🔹 Step 6: When Mixed Types Are Actually Useful

Sometimes, mixed types are intentional.

Example: Configuration settings

config = {
    "debug": True,
    "port": 8080,
    "host": "localhost",
    "timeout": 30.5
}

Here, different types make sense.

Another example: JSON data from APIs.

---

🔹 Step 7: How to Handle Mixed Types Safely

If mixed types are unavoidable, check types first:

value = students["Bob"]

if isinstance(value, Student):
    print(value.exercises)
else:
    print("Not a Student object")

This prevents crashes.

---

🔹 Step 8: Using Type Hints to Avoid Problems

Modern Python supports type hints:

students: dict[str, Student] = {}

This tells tools and editors:

This dictionary should only contain Student objects.

It helps catch mistakes early.

---

🔹 Step 9: Real-World Analogy

Imagine a cabinet labeled “Student Records”.

Inside:

• Folder → Student file ✔️
• Folder → Shopping bill ❌
• Folder → Student file ✔️

Technically possible.
Practically confusing.

Good systems keep things organized.

---

✅ Final Takeaway

Yes, Python dictionaries can store mixed data types:

students["Alice"] = Student(12)
students["Bob"] = 50

But good programming practice is:

✔ Keep values consistent
✔ One dictionary → one main data type
✔ Avoid runtime errors
✔ Improve readability

Rule of Thumb

If your dictionary represents “students”,
store only Student objects in it.

---

[Author]

Posts