LazyDate removal (changeset 4985)
7 views
Skip to first unread message
David Danier
Apr 11, 2007, 9:30:08 AM4/11/07
to django-d...@googlegroups.com
LadyDate was removed in changeset 4985
(http://code.djangoproject.com/changeset/4985). This is great, as the
funciotnality here is not really needed and the new handling using a
callable object is much simpler.
What I'm missing now is the possibility to use callbacks in (new)forms
as well (for initial data). Currently I had to replace LazyDate with
datetime.now(), which is not lazy anymore (datetime.now as used for
models would be lazy). Perhaps this can be changed, too?
(http://code.djangoproject.com/changeset/4985). This is great, as the
funciotnality here is not really needed and the new handling using a
callable object is much simpler.
What I'm missing now is the possibility to use callbacks in (new)forms
as well (for initial data). Currently I had to replace LazyDate with
datetime.now(), which is not lazy anymore (datetime.now as used for
models would be lazy). Perhaps this can be changed, too?
Greetings, David Danier
akaihola
Apr 22, 2007, 9:24:52 AM4/22/07
to Django developers
Just use datetime.now without the function call parentheses.
See
http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#RemovedLazyDate
for an explanation.
David Danier
Apr 22, 2007, 5:05:14 PM4/22/07
to django-d...@googlegroups.com
> Just use datetime.now without the function call parentheses.
Know this, doesn't work for newforms (initial value).
I added a ticket (including a patch) to fix this:
http://code.djangoproject.com/ticket/4018
David
Russell Keith-Magee
May 12, 2007, 11:52:22 AM5/12/07
to django-d...@googlegroups.com
FYI - David's fix was applied to trunk in [5209]. Thanks for the patch, David.
Yours,
Russ Magee %-)
Reply all
Reply to author
Forward
0 new messages