DOH, I thought I tried changing the DATE_FORMAT and it had no effect.
Seems I checked the wrong server when I checked that.
Thanks, it does fix it when you compare output on the right server.
8-|
--
You received this message because you are subscribed to the Google Groups
"Django developers" gr
Thank you for your email.
This is not a bug in Django, it is the correct output when you set
DATE_FORMAT = "%m/%d/%Y". Your desired output will come if you set
DATE_FORMAT = 'm/d/Y'.
The documentation [1] may not be too clear on what formatting is
required, but does give an example which hints at
Recently updated to the latest trunk (couple weeks ago now).
I think this may be a bug in the current trunk.
alist = Table_with_date_column.objects.all()
in template:
{{ alist.date_field }}
renders:
%10/%26/%2009
%07/%22/%2009
...
This must have something to do with the
settings.py
DA
