2012/11/27 Ion Scerbatiuc <[email protected]> > The datetimes in the POST are created using timezone.now() (and I have > USE_TZ = True) >
The POST data simulates the values entered by the user in the form. It should contain naive datetimes in local time. 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 wondering if someone encountered this issue before, or if there is > already a ticket submitted. I personally failed to find one, but maybe I > just suck at searching Trac. > As far as I know, you're the first one to report this problem. We have two options: - improve the code so an aware datetime is accepted as form input, and passed-through unchanged; - document this as a known pitfall. Could you file a ticket in Trac? I'll take a look as soon as possible. -- 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.
