You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
5e9f4c6#diff-80a09bedd7384672dc1f3edebe8107fa26dcc992e71e812dc8b142b0a2ace615L1234 removed the statement series = series.tz_convert(area.tz). Thus, in version 0.6.12 the returned dataframe no longer has a timezone assigned. This was the case in version 0.6.11. I do not believe this change was intended as it changes the format of the returned dataframe.
The text was updated successfully, but these errors were encountered:
hi @bantu many thanks for pointing at this. this was indeed a mistake by me to get the fix quickly out of the door to help people. my apologies!
please note that timezone does not disappear. the results still are timezone aware but they are simply not converted to the local timezone so are always in UTC. I will quickly push a fix
5e9f4c6#diff-80a09bedd7384672dc1f3edebe8107fa26dcc992e71e812dc8b142b0a2ace615L1234 removed the statement
series = series.tz_convert(area.tz)
. Thus, in version 0.6.12 the returned dataframe no longer has a timezone assigned. This was the case in version 0.6.11. I do not believe this change was intended as it changes the format of the returned dataframe.The text was updated successfully, but these errors were encountered: