On Wed, May 28, 2008 at 5:08 PM, Alex Koshelev <[EMAIL PROTECTED]> wrote: > On May 29, 12:57 am, "Leo Soto M." <[EMAIL PROTECTED]> wrote: >> I see that almost all Field subclasses which implements >> get_db_prep_save end calling Field.get_db_prep_save anyway. That's >> curious, because Field.get_db_prep_save is a no-op. >> >> Is it just some OOP style which we want to keep? > > Today it may be empty, but tomorrow there can appear some useful code. > So I think its better to follow that style.
Maybe, but looking at the source code and documentation[1] such super() call is not clearly required. OTOH, if tomorrow a useful code appears, the super() could be added tomorrow. [1] http://www.djangoproject.com/documentation/custom_model_fields/ -- Leo Soto M. http://blog.leosoto.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
