Mixins for reusable behavior in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Django view using a mixin?

Consider this Django view using a mixin to add a greeting message:

from django.views import View

class GreetingMixin:
    def get_greeting(self):
        return "Hello from mixin!"

class MyView(GreetingMixin, View):
    def get(self, request):
        return self.get_greeting()

What will MyView().get(request) return?

Django

from django.views import View

class GreetingMixin:
    def get_greeting(self):
        return "Hello from mixin!"

class MyView(GreetingMixin, View):
    def get(self, request):
        return self.get_greeting()

A "Hello from View!"

B AttributeError: 'MyView' object has no attribute 'get_greeting'

C TypeError: get() missing 1 required positional argument: 'request'

D "Hello from mixin!"

💡 Hint

Check which class provides the get_greeting method and how inheritance works.

The GreetingMixin defines get_greeting. Since MyView inherits from it, calling self.get_greeting() returns the string from the mixin.

📝 Syntax

intermediate

Which option correctly defines a mixin to add a timestamp to a Django model?

You want to create a mixin that adds a created_at timestamp field to any Django model. Which option is syntactically correct and follows Django model mixin patterns?

A

class TimestampMixin(models.Model):
    created_at = models.DateTimeField(auto_now_add=True)

    class Meta:
        abstract = True

B

class TimestampMixin:
    created_at = models.DateTimeField(auto_now_add=True)

C

class TimestampMixin(models.Model):
    created_at = models.DateTimeField(auto_now_add=True)

    class Meta:
        abstract = False

D

class TimestampMixin(models.Model):
    created_at = models.DateTimeField(auto_now=True)

    class Meta:
        abstract = True

💡 Hint

Remember Django mixins for models should be abstract base classes to avoid creating separate tables.

Option A correctly defines an abstract model mixin with auto_now_add=True for creation timestamp. Option A lacks model inheritance. Option A is not abstract, so it creates a table. Option A uses auto_now=True which updates timestamp on every save, not just creation.

🔧 Debug

advanced

Why does this Django view mixin cause a method resolution error?

Given these classes:

class LogMixin:
    def dispatch(self, request, *args, **kwargs):
        print("Logging request")
        return super().dispatch(request, *args, **kwargs)

class MyView(LogMixin, View):
    def dispatch(self, request, *args, **kwargs):
        print("MyView dispatch")
        return super().dispatch(request, *args, **kwargs)

When calling MyView().dispatch(request), a RuntimeError: maximum recursion depth exceeded occurs. Why?

Django

class LogMixin:
    def dispatch(self, request, *args, **kwargs):
        print("Logging request")
        return super().dispatch(request, *args, **kwargs)

class MyView(LogMixin, View):
    def dispatch(self, request, *args, **kwargs):
        print("MyView dispatch")
        return super().dispatch(request, *args, **kwargs)

A Both dispatch methods call super().dispatch(), causing infinite recursion because View does not implement dispatch.

B The mixin LogMixin does not call super(), so dispatch chain breaks causing recursion.

C MyView overrides dispatch but calls super() which calls LogMixin again, causing infinite recursion.

D The method dispatch is missing required arguments, causing recursion error.

💡 Hint

Think about the method resolution order and what happens when super() calls a method that calls super() again.

Both LogMixin and MyView override dispatch and call super().dispatch(). If the base View class does not implement dispatch, super() calls circle back causing infinite recursion.

❓ state_output

advanced

What is the value of self.counter after calling this mixin method twice?

Given this mixin and class:

class CounterMixin:
    def __init__(self):
        self.counter = 0

    def increment(self):
        self.counter += 1

class MyClass(CounterMixin):
    def __init__(self):
        super().__init__()

What is the value of self.counter after this code?

obj = MyClass()
obj.increment()
obj.increment()

Django

class CounterMixin:
    def __init__(self):
        self.counter = 0

    def increment(self):
        self.counter += 1

class MyClass(CounterMixin):
    def __init__(self):
        super().__init__()

obj = MyClass()
obj.increment()
obj.increment()

A 1

B 2

C 0

D AttributeError: 'MyClass' object has no attribute 'counter'

💡 Hint

Check if the mixin's __init__ is called and how increment changes counter.

The mixin initializes counter to 0. Each call to increment adds 1. After two calls, counter is 2.

🧠 Conceptual

expert

Which statement best describes the role of mixins in Django?

Choose the most accurate description of mixins in Django development.

A Mixins replace Django's middleware to handle HTTP requests and responses globally.

B Mixins are Django apps that must be installed to add new features to a project.

C Mixins provide reusable behavior by allowing multiple inheritance of methods and properties without creating separate database tables.

D Mixins are templates that define the HTML structure for multiple views.

💡 Hint

Think about how mixins help share code in classes without affecting database schema.

Mixins are classes designed to add reusable methods or properties to other classes via multiple inheritance, commonly used in Django for views and models without creating new tables.