如何在Python中重构仅AZ后缀不同的Django模型类代码？

Great question—duplicating code like that is never ideal, and Django gives us a couple clean ways to refactor this. Here are two practical approaches you can use:

1. Abstract Base Class (Explicit & Maintainable) #

The simplest and most readable way is to create an abstract base class that holds all the shared fields, then have each AZ-specific class inherit from it. This keeps your code DRY (Don’t Repeat Yourself) while remaining easy to follow for other developers.

from django.db import models

class BaseNovaAZ(models.Model):
    sampleTime = models.BigIntegerField(default=0)
    status = models.FloatField(default=0)

    class Meta:
        abstract = True  # Marks this as a base class that won't create its own database table

# Each AZ class is now a minimal subclass
class Nova_AZ0(BaseNovaAZ):
    pass

class Nova_AZ1(BaseNovaAZ):
    pass

class Nova_AZ3(BaseNovaAZ):
    pass

If you ever need to add class-specific behavior (like custom Meta options or methods) to one of the AZ classes, you can easily extend that subclass without affecting the others.

2. Dynamic Class Creation (For Scalability) #

If you anticipate needing more AZ classes in the future, you can generate them programmatically in a loop. This reduces boilerplate even further, though it’s a bit more "magic"—use it only if clarity isn’t compromised.

from django.db import models

# Define shared fields once
shared_fields = {
    'sampleTime': models.BigIntegerField(default=0),
    'status': models.FloatField(default=0),
    '__module__': __name__,  # Critical: tells Django where the model is defined
}

# List of AZ suffixes you need
az_suffixes = [0, 1, 3]

# Dynamically create each model class
for suffix in az_suffixes:
    class_name = f'Nova_AZ{suffix}'
    # Create the class and add it to the global namespace
    globals()[class_name] = type(class_name, (models.Model,), shared_fields)

This will create the exact same Nova_AZ0, Nova_AZ1, and Nova_AZ3 classes as your original code, but without repeating field definitions. Just ensure this code lives in your models.py so Django’s model discovery system can find it.

Which to Choose? #

• Use the abstract base class if you want explicit, easy-to-read code (great for small numbers of classes or when you might need per-class customizations).
• Use dynamic creation if you have many AZ classes or want to generate them from a config/setting.

内容的提问来源于stack exchange，提问作者edison xue