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
I encountered the following after upgrading to Pandas 0.21. Essentially 2 issues:
The problem is when I have a Dataset with one of the coords as pd.DatatimeIndex, calling DataArray.to_dataframe() produced a pd.DataFrame with MultiIndex, rather than DatetimeIndex before the upgrade.
DataArray.to_dataframe() also behaves differently comparing to DataArray.to_pandas().
The below example reproduces both issues. Shouldn't both method be returning DatetimeIndex-ed data frames? My current hack is to manually convert the MultiIndex back to DatetimeIndex.
I suspect this is something related to the new Pandas but don't see any obvious links. Would someone be able to shed some light on this?
Hi all,
I encountered the following after upgrading to
Pandas 0.21
. Essentially 2 issues:The problem is when I have a
Dataset
with one of thecoords
aspd.DatatimeIndex
, callingDataArray.to_dataframe()
produced apd.DataFrame
withMultiIndex
, rather thanDatetimeIndex
before the upgrade.DataArray.to_dataframe()
also behaves differently comparing toDataArray.to_pandas()
.The below example reproduces both issues. Shouldn't both method be returning
DatetimeIndex
-ed data frames? My current hack is to manually convert theMultiIndex
back toDatetimeIndex
.I suspect this is something related to the new
Pandas
but don't see any obvious links. Would someone be able to shed some light on this?EDIT: I suspect if this is related to this change: MultiIndex Constructor with a Single Level?
Much appreciated.
The text was updated successfully, but these errors were encountered: