On 6/27/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Looks like this is the default result for Model subclasses. Possibly > related to the way we create them (using a metaclass). Feel free to work > out a patch in django/db/models/base.py (in the ModelBase class, > probably) if you want to fix this. It would probably be useful.
I've seen it happen as well, always on model classes. I need to check a newforms form and see if the same happens to them. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
