On Sun, Mar 15, 2009 at 2:44 PM, Dan Watson <dcwat...@gmail.com> wrote:
> > On Mar 15, 1:12 pm, "Gary Wilson Jr." <gary.wil...@gmail.com> wrote: > > What do you think? > > Wouldn't this be a backwards-incompatible change at this point? It > would clash with any model fields named "update". > > Dan > > > Take a look at the backwards compatibility policy, it outlines that we don't consider the APIs complete, and that we can add stuff in the future: http://docs.djangoproject.com/en/dev/misc/api-stability/ Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
