html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/pull/961#issuecomment-271432556,https://api.github.com/repos/pydata/xarray/issues/961,271432556,MDEyOklzc3VlQ29tbWVudDI3MTQzMjU1Ng==,1217238,2017-01-09T22:47:08Z,2017-01-09T22:47:08Z,MEMBER,"NumPy's datetime64 is timezone naive, though indeed using UTC is generally the recommended approach. Storing timezones would need to done with another metadata layer or could be done by storing an object array of `datetime.datetime` or `pandas.Timestamp` objects.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,170688064
https://github.com/pydata/xarray/pull/961#issuecomment-271420374,https://api.github.com/repos/pydata/xarray/issues/961,271420374,MDEyOklzc3VlQ29tbWVudDI3MTQyMDM3NA==,1117224,2017-01-09T21:57:13Z,2017-01-09T21:57:13Z,NONE,"Numpy's datetime64 dtype currently used by xarray does not store time zone as mentioned here #552. To prevent users from making time zone errors upon dataset creation, I think the implied assumption that UTC be used, should be made more apparent in the readthedocs. Hopefully in the future it can be added to datetime64??","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,170688064
https://github.com/pydata/xarray/pull/961#issuecomment-269094525,https://api.github.com/repos/pydata/xarray/issues/961,269094525,MDEyOklzc3VlQ29tbWVudDI2OTA5NDUyNQ==,2443309,2016-12-24T18:05:35Z,2016-12-24T18:05:35Z,MEMBER,"@NicWayand - when you have a minute, fix the typo that @MaximilianR mentioned and possibly expand the discussion a bit. Then we'll be happy to merge this in.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,170688064