0

I'm working with an API that passes me a time/date field that they cannot guarantee will always have timezone info in it.

From their docs, this field could be either:

Empty String,
YYYY-MM-DD,
YYYY-MM-DDTHH:MM:SS, or
YYYY-MM-DDTHH:MM:SS+TIMEZONE

When I try to save that field to my model in the database it generates this error in the case where the data comes without timezone information. The field I'm saving this value into is defined in its model as:

my_timedate_field = models.DateTimeField()

At a minimum I'd like to suppress the warnings from being generated with each record saved. Is there anything specific I can do to make this a bit cleaner?

Edit: The warnings are:

RuntimeWarning: DateTimeField my_timedate_field received a naive datetime while time zone support is active. RuntimeWarning)

These warnings show up in my logs every time I process an api call -- sometimes 5-10 times per api call given how the elements show up.

Kevin Bedell
  • 13,254
  • 10
  • 78
  • 114
  • What are the warnings you want to remove ? I think you could use a date_parser with a few try, to parse the correct time format since they all seem to be identifiable – WNG Nov 30 '17 at 17:05
  • I've added the specific warning info in the question. – Kevin Bedell Nov 30 '17 at 18:30
  • Possible duplicate of https://stackoverflow.com/questions/18622007/runtimewarning-datetimefield-received-a-naive-datetime. – Masood Khaari Feb 24 '18 at 15:48

1 Answers1

3

I figured this out.

It turns out that -- assuming I can't count on timezone info always being a part of the string passed from the incoming API -- this is the best I can do.

By using the django model declaration:

api_time = models.DateTimeField()

time values sent in that do not contain timezone info can still be stored in that field. The warning occurs to let you know that you are saving a non-timezone field in a timezone-aware database field.

Again -- here's the warning:

RuntimeWarning: DateTimeField api_time received a naive datetime 
  (2018-08-03 09:04:25) while time zone support is active.
Kevin Bedell
  • 13,254
  • 10
  • 78
  • 114
  • 1
    You can fix this warning with the answer for this question: https://stackoverflow.com/questions/18622007/runtimewarning-datetimefield-received-a-naive-datetime – iperetta Feb 18 '19 at 12:56