I'm a little unsure whether that argument continues to hold about users
writing times and dates. I don't know of that many sites which don't use a
datepicker of some description at least for dates, and even the admin has
some client side help for picking times.
It seems reasonable that one field
Django’s DateTimeField parsing code is really targeted at values typed by
humans. It doesn’t handle time zones because humans don’t tend to write them
down :)
Wouldn’t it be easier to write an ISODateTimeField? It could take advantage of
django.utils.dateparse.parse_datetime, which parses an
Hi everyone, I wanted to bring up a request: Ticket #11385 dealt with
Django's DateTimeField being unable to handle ISO 8601 date formats.
At the time it seemed reasonable to not support this feature given,
however, given the proliferation of web service APIs that return dates
using this format,
