On 4/2/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > On 4/1/07, SmileyChris <[EMAIL PROTECTED]> wrote: > > I'm not sure if there's a ticket for this, but I remember talk about > > it being an unnecessary wart which was going to be removed eventually. > > Is it in the 1.0 plan? > > Yes, I'd like to drop those two options. > > auto_now can be accomplished with "default=datetime.datetime.now", and > auto_now_add can be accomplished with a custom save() method.
What about LazyDate? It seems to me that given "default=datetime.datetime.now" is legal, LazyDate can be deprecated as well. Yours Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
