On Mon, 2007-04-02 at 09:00 +0800, Russell Keith-Magee wrote: > 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.
Is there an easy way to say "today - 3 days" just using the datetime module? I can't think of one off the top of my head that isn't as complex as LazyDate(), but that may be because it's Monday. At the moment LazyDate is useful in limit_choices_to and as a default value. I'd vote to move it into django/utils/dates.py so that it's more visible (it feels wrong in models/__init__.py, but that may just be my bad taste), but I'd like to keep it. Otherwise I'm pretty sure I'm going to end up rewriting it for myself. Cheers, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
