I a model that requires both timezone aware and naive datetimes. To be 
specific, I am modelling a travel segment where the standard for departure 
and arrival is to always use current local time, regardless of tz/dst/&c as 
well as an approved_on field that should have a tz.

Is there anyway to declare the desired timezone support for the datetime 
field in the model? I'm trying to avoid "RuntimeWarning: DateTimeField 
XXX.timestamp received a naive datetime" warning spam in my output.


-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/a24aa1dd-95a1-47ba-93fc-01841b982083%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to