2012/11/27 Ion Scerbatiuc <[email protected]> > Actually, to be realistic, it should contain strings representing naive >> date times, because that's what will be POST-ed by a HTML form. But using a >> datetime object works too. >> > > I'm not 100% sure that the datetimes received in the POST should represent > naive date times. I mean there might be use cases when they represent aware > datetimes: > > - there is a custom widget that allows the user to specify the timezone > - the data is coming through a REST API and you have a form handling > the validation > - ... > > Indeed, if the string contains timezone information (ie. Z or +03:00), Django should take it into account.
-- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. 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.
