Question

NOTE: this was asked before AbstractUser existed, which is probably what you’d want to use these days.

Basically I would like to delete the default email field from the default Django User class…

class MyUser(User):
    field = models.CharField(max_length = 10)
    a = 'hello'
    def b(self):
        print 'world'

del User.email
del MyUser.email
del Myuser.field

All these give AttributeError. Deleting methods or attributes in the following way though works fine:

del MyUser.a
del MyUser.b

So I’m curious why this doesn’t work; what type of things are these model fields?

Another thing I tried was overwriting email by creating an email = None in MyUser but that didn’t work either (and would be slightly more ugly).

Thanks in advance!

P.s. If you are wondering why; it’s more for curiousity than that it is really necessary for the application… But I think it’s good not to have unused columns in database.
P.p.s. I don’t want to change the Django files to manually remove ’email’ from user.

EDIT: Follow-up question here (for those who want to do the same thing) Before syncdb, delete field from standard Django model

Answer 1

As you’ve discovered, model fields aren’t actually class attributes, even though they appear to be.

Models are constructed by some very clever but complicated hacking around with metaclasses. When a model class definition is executed (the first time its models.py is imported), the metaclass runs through all the field definitions for that model, and calls the contribute_to_class method of each one. This ends up putting the actual fields into the new class’s _meta.fields property. So the model class itself doesn’t have the fields as direct properties.

Then, when a model instance is actually instantiated, Django takes that list and directly sets the new instance’s attributes, using either the arguments to the constructor or the default values supplied by the fields. So, the value that’s accessed via the instance has no actual field code behind it: it’s a simple instance attribute.

Anyway, the upshot of all this is that to remove a field from a model definition you just need to delete it from the Model._meta.fields list.