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
In 0.19.1 appending a DateTimeIndex to another DateTimeIndex where they have different time zones now returns an Index object. In 0.18.1 it would return a DateTimeIndex with a UTC time zone.
In 0.19.1 (and in 0.18.1) if the two DateTimeIndex have the same time zone a DateTimeIndex is returned. I believe the behavior in 0.18.1 of returning a DateTimeIndex with time zone UTC should be the correct behavior.
The text was updated successfully, but these errors were encountered:
rsheftel
changed the title
Append with two DateTimeIndex converst to Index and not DateTimeIndex
Append with two DateTimeIndex returns Index and not DateTimeIndex
Dec 3, 2016
Appending different timezones and coercing to UTC loses information. It is up to the user to explicitly coerce to the same timezone if you don't want this behavior. Having mixed timezones within a single object is only supported with boxed objects, hence the object dtype.
In 0.19.1 appending a DateTimeIndex to another DateTimeIndex where they have different time zones now returns an Index object. In 0.18.1 it would return a DateTimeIndex with a UTC time zone.
In 0.19.1 (and in 0.18.1) if the two DateTimeIndex have the same time zone a DateTimeIndex is returned. I believe the behavior in 0.18.1 of returning a DateTimeIndex with time zone UTC should be the correct behavior.
--- Example of the problem ---
The text was updated successfully, but these errors were encountered: