在PyCharm运行Django应用执行syncdb时遇SubfieldBase属性不存在错误

Hey there, let's tackle this error you're hitting when running python manage.py syncdb in PyCharm. This issue pops up because SubfieldBase was deprecated in Django 1.8 and fully removed in Django 1.10+—so if you're using a newer Django version, any code (yours or from a third-party package) relying on this old API will break.

Here's how to fix it, depending on where the problem originates:

1. The issue is in your custom field code #

If you wrote a custom model field using @with_metaclass(models.SubfieldBase...) or setting __metaclass__ = SubfieldBase, you need to replace that outdated pattern with Django's modern field handling methods.

Before (old code causing the error): #

from django.db.models import SubfieldBase
from django.utils.six import with_metaclass

@with_metaclass(models.SubfieldBase, skip_attrs=set([...]))
class MyCustomField(models.Field):
    # Your field logic here

After (updated code for Django 1.8+): #

Remove the metaclass decorator entirely, and implement these two methods instead:

class MyCustomField(models.Field):
    def to_python(self, value):
        # Handle conversion from user input/serialized data to Python object
        if value is None:
            return value
        # Add your existing conversion logic here
        return processed_value

    def from_db_value(self, value, expression, connection):
        # Handle conversion from database value to Python object
        # This replaces the automatic handling that SubfieldBase provided
        return self.to_python(value)

The from_db_value() method handles data loaded from the database, while to_python() manages data from forms or serializers—together they replicate what SubfieldBase used to do automatically.

2. The issue is from a third-party package #

If the error comes from an installed library (not your own code), you have a few options:

• Upgrade the package: Check for a newer version of the library that supports your Django version. Most popular packages have updated to remove SubfieldBase dependencies.
• Patch the package manually: If the package is unmaintained, you can fork it or edit the local installation to replace SubfieldBase usage with the to_python()/from_db_value() pattern shown above.
• Downgrade Django (last resort): If you must use an unmaintained package, you can downgrade Django to 1.7 or earlier—but this isn't recommended, as older versions no longer receive security updates.

Quick side note: #

Also, python manage.py syncdb is deprecated in Django 1.9 and later. You should use python manage.py migrate instead to apply database migrations.

Hope this resolves your error and gets your Django app running smoothly!

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